Use the agreement MCP

MCP (Model Context Protocol) connects your AI assistant to the Cofounder Community agreement library and a private drafting workspace. Work conversationally with Claude or another compatible assistant: it can find source documents, explain choices, prepare review drafts and call the tools as needed.

The recommended workflow is discuss → choose templates → draft → review → save → export → counsel approval.

Connect your assistant

In an assistant that supports remote MCP connections and OAuth sign-in, add this server address:

Private drafting and saved agreements: https://mcp.cofounder.community/mcp

Sign in through Intergraph and review the requested access. The consent screen identifies the connected client and the agreement-read and private-draft permissions it requests. You do not need to paste a password or API token into your conversation.

Public library browsing, without an account: https://mcp.cofounder.community/mcp/public

Both addresses use Streamable HTTP. Add them through your assistant's MCP connection settings; they are tool endpoints, not ordinary webpages. Setup labels and file-download support vary between clients. If your client only supports public connections, use the browsing address to explore the library.

Technical setup: Claude web and Desktop

1. Open Customize → Connectors in Claude, then + Add → Add custom connector.
2. Name it Cofounder Agreements and enter https://mcp.cofounder.community/mcp as the remote server URL.
3. Continue through discovery. Choose Sign in now and, under OAuth client, choose Register automatically. This service supports automatic registration of public OAuth clients; use that option rather than Claude's published client identity. Leave fixed request headers and manual client credentials empty.
4. Finish adding the connector, sign in through Intergraph and approve the requested access on the Cofounder consent screen.
5. Enable the connector for your conversation through the chat's + → Connectors menu. Ask: “Use Cofounder Agreements to find a provisional offer letter and show its source.”

For browsing only, add the public URL instead and choose No sign in. Team or Enterprise administrators may need to add the connector before members can connect. Interface labels can change; see the official Claude connector instructions.

Technical setup: Claude Code

With Claude Code installed, run this in your terminal to make the hosted connection available across your projects:

claude mcp add --transport http --scope user cofounder-agreements https://mcp.cofounder.community/mcp
claude mcp get cofounder-agreements

Start Claude Code with claude, enter /mcp, select cofounder-agreements, and complete its browser authentication flow. No custom Authorization header or client secret is required. Return to the client after Intergraph sign-in and consent.

For an unauthenticated browsing connection instead, run:

claude mcp add --transport http --scope user cofounder-public https://mcp.cofounder.community/mcp/public

Alternatively, for a project-scoped connection, merge this entry into the project's .mcp.json file. Do not overwrite other configured servers. Authenticate through /mcp after the configuration is loaded.

{
  "mcpServers": {
    "cofounder-agreements": {
      "type": "http",
      "url": "https://mcp.cofounder.community/mcp"
    }
  }
}

These are Claude Code configurations, not a remote-server entry for claude_desktop_config.json. Use Claude's custom connector UI for the hosted Desktop connection. See the Claude Code MCP reference for configuration scopes and authentication recovery.

Technical setup: VS Code and other clients

In VS Code, run MCP: Add Server from the Command Palette, select HTTP, enter the authenticated server URL, and name it cofounder-agreements. Choose the configuration location, then start the server and follow its authentication prompts. The project .mcp.json example above is also supported by current VS Code; its VS Code-specific .vscode/mcp.json format uses a top-level servers object instead. See the VS Code MCP instructions for your version and environment.

For another client, use these connection settings. Its own documentation determines the exact configuration file format.

For a custom OAuth implementation, register a public client with token_endpoint_auth_method=none and an HTTPS or loopback HTTP redirect URI. The resource identifier is exactly https://mcp.cofounder.community/mcp. Discover the OAuth endpoints from https://mcp.cofounder.community/.well-known/oauth-authorization-server and resource metadata from https://mcp.cofounder.community/.well-known/oauth-protected-resource/mcp. Let the client handle tokens and refresh; do not use an Intergraph login token or a deployment credential as an MCP bearer token.

Verify the connection

Ask the connected assistant: “List the Cofounder agreement tools and search for a provisional offer letter.” Public connections expose search_agreements, get_agreement, get_bundle, compare_agreements and get_drafting_fields. Authenticated connections also expose draft generation, private save/retrieval/update/deletion and export tools; updating a draft uses save_draft.

Developers can check the hosted service without credentials:

curl --fail-with-body https://mcp.cofounder.community/health

An MCP initialize request to the public endpoint verifies protocol access:

curl --fail-with-body https://mcp.cofounder.community/mcp/public \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"connection-check","version":"1.0"}}}'

The result includes the server's name, capabilities and negotiated protocol version. This service uses stateless JSON responses; a plain browser GET to an MCP endpoint returns 405, and an unauthenticated POST to the private endpoint returns 401. Both are expected. It does not offer a legacy /sse endpoint. Full MCP clients should perform the normal initialization handshake and protocol-version negotiation.

Troubleshooting connections

• No tools appear: check the full URL, select HTTP/Streamable HTTP, start or reconnect the server, and enable its tools in the conversation. For private drafting, complete authentication first.
• Unknown OAuth client or a request for credentials: choose Register automatically in Claude. The server does not require you to supply a pre-created client ID, client secret or fixed bearer token.
• 401 or expired authentication: reconnect or re-authenticate in your client, then repeat the request. Do not paste tokens into chat.
• 403 or “Origin not permitted”: use the native MCP connector rather than a browser fetch or embedded web widget. Custom browser-based clients require an explicitly allowed origin; contact the maintainer instead of disabling origin checks.
• Browser callback to localhost fails: keep the requesting local client running on the same computer as the browser. Follow that client's callback-recovery instructions. Only return a callback URL to the requesting client's own authentication prompt; do not post it in chat or share it publicly.
• A localhost server cannot connect from Claude: Claude's hosted custom connectors reach servers from Anthropic's infrastructure. Use the public HTTPS address above. Local stdio configuration is a separate developer option.
• Only browsing tools are available: you connected to /mcp/public. Use /mcp and sign in for drafting and private storage.
• Saved drafts are missing: check that you signed in with the same Intergraph identity. Local stdio workspaces are separate from hosted accounts.
• An export does not appear as a download: save the draft first. The service returns base64-encoded file bytes to the client; file decoding and download presentation depend on the client. Exported files are not public URLs.

Optional: run the service locally

Hosted users do not need to install this repository or run a server. Developers who want a local copy need Node.js 22.13 or newer. From the repository root:

npm ci --prefix mcp
npm start --prefix mcp

The default public endpoint is http://127.0.0.1:8020/mcp/public. Local authenticated HTTP drafting additionally needs the Intergraph environment configuration. Local stdio clients can launch node with the absolute path to mcp/src/stdio.mjs; their workspace is local and separate from your hosted Intergraph account. Saving requires a stable, locally managed encryption key. See the local setup instructions for configuration; keep keys out of shared client files.

1. Describe the situation

Start with your objectives rather than a request to fill in a form. Explain the parties and entities, where people work, the intended relationship, responsibilities, timing, compensation, equity and any funding or revenue conditions. Supply the facts you know and ask the assistant to identify missing decisions.

Help me structure an engagement for a business leader. Ask me about missing material facts before recommending documents. I want to understand the relationship, cash compensation, equity and approvals we need to address.

2. Choose templates and companion documents

Ask the assistant to search the library, read the canonical templates and completion guides, compare alternatives and identify the other documents needed for the transaction. Ask it to cite the template version and source links so you can inspect the underlying language.

Find the relevant offer, consulting and equity documents. Explain their differences, compare the relevant source clauses and suggest a document bundle. Flag decisions for each party's counsel.

The assistant supplies the reasoning. The MCP supplies published sources, guides, comparisons and drafting tools. A recommended template is a starting point for review, not a conclusion that it is suitable for your circumstances.

3. Agree on the terms, then draft

Ask for a plain-language summary of the proposed terms before generating a document. Resolve material choices first. The assistant can discover the template's fill-in fields, replace placeholders and make explicit section revisions. Missing information stays clearly marked; it should not invent facts, dates, approvals or legal conclusions.

Summarize our agreed terms and list unresolved decisions. Once we have reviewed them, prepare a draft from the selected template. Preserve unresolved placeholders and explain any changes to the source language. Do not save it yet.

For provisional offers, a dedicated generator supports funding or revenue thresholds, prospective monthly compensation without prior accrual, and optional initial and performance equity. It supports up to three increasing cash tiers; its structured equity schedule uses four-year vesting with a one-year cliff. Ask about employee or consultant classification, lawful arrangements before a cash trigger, the revenue definition, share capitalization and required corporate approvals before drafting.

4. Review and revise together

Read the draft with the assistant. Check names, entities, dates, definitions, thresholds, compensation, vesting and companion documents. Ask for an explanation of changes from the template, a list of unresolved blanks and questions for counsel. Discuss revisions before updating a saved draft.

Review this draft for internal inconsistencies. Show what changed from the template, list every unresolved field and prepare questions for each party's independent counsel.

These checks help organize review; they do not establish legal validity, lawful classification or completed approvals.

5. Save only when you ask

Generating a draft does not save it to the MCP workspace. Explicitly ask to save when you want to retain it. Saved drafts are encrypted and scoped to your verified Intergraph identity. You can list, retrieve, revise or delete your drafts later, including from another connected client signed into that same identity.

Save this draft privately as “Business leader engagement.” Next time, help me retrieve it and continue reviewing the open questions.

The connected assistant receives the facts you share and any draft or export you ask it to retrieve. Your assistant provider's own data-handling settings still apply. The MCP's save-on-request behavior does not control whether that provider retains your conversation. Deleting a saved draft is permanent; download a copy first if you need to keep it. Draft updates are not a full version-history or document-comparison system.

6. Export for counsel review

Ask to save the current draft, then export it as Word, PDF or Markdown. Word is useful for counsel's edits. Exports are returned to your connected client, without creating a public download link. How the assistant presents a downloadable file depends on that client's capabilities.

Save the current revision and export an editable Word copy for counsel, plus a PDF for reading. Include the unresolved terms and the counsel-review disclaimer.

Have every party's own independent legal counsel review and approve the completed document and companion arrangements before any real-world use. Resolve all blanks and obtain the necessary approvals before signing or relying on it.

A prompt to start with

Use the Cofounder Community agreement tools to help me structure an engagement. First understand my objectives and ask about missing material facts. Find the relevant templates and companion documents, explain the choices, and summarize the proposed terms before drafting. Cite the source versions, preserve unresolved placeholders, and explain changes from the templates. Do not save anything until I ask.

What is supported today

• Search and read the published agreement library, completion guides, source versions and available earlier editions.
• Compare source sections, identify transaction bundles and discover template placeholders.
• Generate review drafts from templates, including structured provisional offers with conditional compensation and optional performance equity.
• Save, retrieve, update and delete private drafts after sign-in, and export saved drafts as Word, PDF or Markdown.

The service does not provide legal approval, electronic signatures, filings, automatic share issuance, or monitoring of fundraising, revenue or vesting milestones. It does not import counsel's Word edits or provide tracked-change redlines. The connected assistant can help discuss revisions; the final documents and approvals require independent review.

Open templates and private drafts

The Awake template language remains open under CC BY 4.0, with attribution to AwakeVC. Private facts, completed commercial terms and signatures are not dedicated to public reuse by the template license. Browse the agreement library to inspect and download the public sources directly.

Developers can also run the MCP locally. See the service setup, tools and deployment instructions for HTTP and local stdio configuration.