Blueprint MCP Connector

The Blueprint MCP Connector links Claude directly to your Blueprint corpus, so when you ask Claude a question about your documented processes, systems, or people, it can answer from your own institutional knowledge instead of guessing.

MCP — short for Model Context Protocol — is an open standard that lets AI assistants like Claude call approved tools on remote servers. Prairie Forge operates an MCP server that exposes a small set of read-only tools against your Blueprint data. When you install the connector in Claude, Claude can use those tools during your conversations.

The connector is read-only, invite-gated, scoped to your customer corpus when you connect, and logs every call.

Once connected, you can ask Claude questions grounded in your Blueprint corpus. Examples:

• "Walk me through how month-end close works for AR."

• "Which systems does the revenue cycle touch?"

• "Who owns the customer credit hold process?"

• "Pull the documentation on our trial-balance reconciliation."

• "What projects are active in the controllership team right now?"

Claude returns answers with citations back to the source process step or document.

The connector exposes 10 read-only tools, grouped by purpose.

Search and retrieval:

• search_documents — semantic search across your document corpus

• search_outlines — semantic search across your process outlines

Process documentation:

• list_processes — every documented business process

• list_outline_steps — the steps inside any outline

Documents:

• list_documents — paginated index of your corpus

Organizational context:

• get_people_directory — people, roles, ownership

• get_systems_catalog — systems and tools in use

• get_locations — physical and organizational locations

• get_projects — project register

A tenth tool, list_customers, is reserved for Prairie Forge staff use; customer tokens cannot call it.

The active tool inventory and full data-handling details are covered in our MCP Connector Policy at prairieforge.ai/legal/mcp-connector.

The connector cannot write to your Blueprint corpus. Every tool is read-only.

Your customer-scoped token cannot reach another customer's data. Every query is filtered server-side by your customer identifier before any data leaves our database, and an automated check verifies this enforcement on every code change.

The connector cannot access internal Prairie Forge content — vendor coordination, prospect conversations, partnership communications. That content is held in different systems that the MCP server does not query.

The connector cannot read secrets, API keys, encrypted prompts, or other operational state.

The connector cannot initiate sessions on its own. Claude can only call these tools when a user with a valid token has started a conversation.

Blueprint is a process-documentation product, not an accounting system. We don't ingest raw transactions, ledgers, or balances into your corpus by default — those live in your source systems (NetSuite, Sage Intacct, QuickBooks, and similar) which the connector does not proxy.

If you have uploaded a document that contains transactional data — a sample export, a closing memo with line items, a reconciliation worksheet — the connector reads that document like any other. The corpus boundary is what you have documented; the connector returns what is there.

Step 1 — Request access: Email your Prairie Forge engagement lead. We mint an invite bound to your email and your Blueprint customer scope. Two Prairie Forge staff members must sign off before the invite is issued.

Step 2 — Open the invite link: You will receive an email with a one-click URL. Open it in a browser where you're already signed in to Blueprint as the named recipient — anyone else holding the URL cannot complete the claim flow.

Step 3 — Copy the server URL: The page displays your MCP server URL. Copy it.

Step 4 — Add the connector in Claude: In Claude.ai, open Settings → Custom Connectors → Add Connector. Paste the URL and click through Claude's prompts.

Step 5 — Authorize: Claude will redirect you back to Prairie Forge to confirm the connection. Click Authorize. Claude can now query your Blueprint corpus.

Step 6 — Try it out: Ask Claude a question only your team would know the answer to. For example, "What is the process for closing AR at month-end, and who owns it?"

Dual approval before issuance: Every invite is initiated by one Prairie Forge staff member and confirmed by a different one. No single Prairie Forge staff member can mint an invite alone.

Token scope and lifetime: Access tokens last one hour. They are refreshed automatically against a 30-day sliding window of activity. Tokens are audience-bound to the MCP endpoint and cannot be replayed against other Prairie Forge services.

Revocation: Connections are revocable through our admin surface. Revocation prevents new token issuance immediately. Any access token already in flight expires within its one-hour lifetime, after which the connection is fully cut off. Email connect@prairieforge.ai to request a revocation.

Staff access: Prairie Forge engagement staff can also query your Blueprint corpus when servicing your account. Every staff query requires a structured reason code, names your customer identifier explicitly, and is recorded in a separate audit log. We will share that log with you on request.

Every tool call writes an audit record containing the caller's identity, the customer scope, the tool name, the timestamp, the result count, and the execution duration.

For search tools, the free-text query you pass to Claude is stored as a one-way hash (SHA-256) rather than in readable form. Other tool inputs — pagination limits, filters, staff customer identifiers, staff reason codes — are stored as written for audit purposes.

Logs are retained for security review and audit. You can request a copy of your organization's MCP audit log at any time by emailing connect@prairieforge.ai.

I pasted the URL but Claude can't find the connector: Check that you copied the full URL from the connection page (the long one starting with https://). If Claude still cannot reach it, the invite may have expired — email your engagement lead for a fresh one.

Claude is asking me to log in again: Access tokens last an hour by design. Claude refreshes them automatically in most cases; if you go offline overnight, you may need to re-authorize the connector once.

A tool returned "no results": Your query did not match anything in your documented corpus. Try rephrasing — the search tools work best when the wording is close to what your team has documented.

Can I add a teammate: Yes. Each person needs their own invite, bound to their own email. Contact your engagement lead to request additional access.

How do I disconnect: In Claude.ai, remove the connector from Settings → Custom Connectors. To fully revoke the underlying token on our side, email connect@prairieforge.ai.

The connector follows the same security standards as the rest of Blueprint. For full details on data handling, audit logging, customer scoping, token lifecycle, and the third-party providers involved, see:

• MCP Connector Policy — prairieforge.ai/legal/mcp-connector

• AI Policy — prairieforge.ai/legal/ai-policy

• Privacy Policy — prairieforge.ai/legal/privacy

• Security Policy — prairieforge.ai/legal/security

Email connect@prairieforge.ai. We respond to MCP-specific inquiries within 48 hours.