Setup guideAbout 2 minutesLast checked 12 October 2026

Connect CaptableAI to any MCP client

Any client that speaks MCP, plus the CLI for scripts. Once it's connected, ask about your equity in plain language, upload documents, model a round and export the result, all from the same chat.

Short answer

Point any client that supports remote MCP at https://mcp.captable.ai/mcp (Streamable HTTP, OAuth). If your client only runs local servers, bridge it with npx mcp-remote. For scripts and CI, use the CaptableAI CLI.

What you need

✓An MCP client, or Node.js for the bridge and CLI.
✓A CaptableAI company where you are an owner or admin.

Set it up

Try the URL first

Clients with remote MCP support need only the endpoint. The transport is Streamable HTTP and sign-in is OAuth.

Server URL

https://mcp.captable.ai/mcp

Bridge stdio-only clients

mcp-remote runs locally and forwards to the hosted server, handling the OAuth sign-in for you.

MCP client config

{
  "mcpServers": {
    "captable-ai": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.captable.ai/mcp"]
    }
  }
}

Scripting or CI? Use the CLI

@fairmint/captable-ai runs the same operations from the terminal, and it's the way to upload files between 25 MB and 50 MB.

Terminal

npx @fairmint/captable-ai --help

Sign in

Every route uses the same OAuth flow against your existing CaptableAI account.

Check it worked

Ask your client to list its tools. You should see CaptableAI's tools for reading, uploading, modelling and exporting.

First things to ask

“Run extraction on everything classified, then commit once every document reaches PROCESSED.”

“Show me fully diluted ownership by share class.”

“Export the shareholder register as a PDF.”

Troubleshooting

Which transport does CaptableAI use?

Streamable HTTP at /mcp, with OAuth for sign-in.

My client only supports local servers.

Use the mcp-remote configuration above. It runs on your machine and forwards requests to the hosted server.

Files over 25 MB won't upload.

That's the limit through MCP. The CLI accepts files up to 50 MB.

Then: upload your documents

CaptableAI builds your cap table by reading your legal documents. These seven habits keep it fast and accurate. Share them with your client.

01 Upload everything first +

Add all of your cap table documents up front, in one batch where possible: incorporation documents, SAFEs, stock and option agreements, board consents. PDF, DOCX, XLSX, DOC and images are supported.

02 Wait for classification +

Each document is read and classified, so the system knows its type and effective date. Don't trigger extraction until every document shows CLASSIFIED.

03 Check the classification dates +

The effective date decides processing order. If one looks wrong, fix it before extraction so the cap table is built in the right sequence.

04 Trigger extraction once +

Extraction doesn't start automatically for agent uploads. Trigger it a single time after everything is classified; the whole queue is picked up.

05 Let the queue run +

Documents are extracted one at a time, earliest first, so later events build on earlier ones. Expect a few minutes per document and don't re-trigger.

06 Validation runs on its own +

When the last document finishes, a company-wide validator checks every extracted object and repairs cross-document issues. There's nothing to trigger.

07 Review, then commit +

When every document reaches PROCESSED, review the drafts and commit. The first commit activates your cap table.