MCP Server

Caplia is an MCP server for founders to improve their own company. Point Claude Desktop, Cursor, ChatGPT, or any MCP client at the Caplia MCP server with a founder key, and the agent can read your CRI score, explain the rubric’s recommendations, and run the private deck-scoring loop - regenerating your pitch deck between scores until it clears Caplia Verified. It’s the same MCP server and the same hosts as the Venture API, but your key decides what you get: a cap_fnd_* key sees the founder toolset below, scoped to your one company.

What you can do

Iterate your deck to 700

“Score my deck privately, rebuild the weak slides in Canva to address the feedback, and resubmit until my CRI is at least 700.” The agent loops caplia_submit_deck_draft → caplia_get_deck_draft → publish.

Understand your score

“What’s my CRI and what’s holding it back?” The agent calls caplia_get_my_scores and walks you through each domain and recommendation.

Keep your profile current

“Update my stage to Series A and fix my website.” The agent calls caplia_update_my_company.

Manage your data room

“Upload this financial model to my data room.” The agent calls caplia_upload_document - which also unlocks the financial-model points in your CRI.

Endpoints

Production:    https://mcp.venture.caplia.ai/
Sandbox:       https://mcp-sandbox.venture.caplia.ai/

Transport: Streamable HTTP (single POST endpoint, JSON-RPC 2.0). The server supports MCP protocol revisions from 2024-11-05 to 2026-07-28.

The Founder API is live in production. Keys you create in the Caplia app at app.caplia.ai are live cap_fnd_live_* keys, and they work on the production host only. The sandbox host takes cap_fnd_test_* keys from Caplia’s staging environment and is meant for developers testing an integration. The deck-loop tools need a key with the write scope.

Authentication

Every request needs a founder key, including initialize and tools/list. A request without one gets HTTP 401 with a WWW-Authenticate challenge that points to /.well-known/oauth-protected-resource. There are two ways to send the key, and both give the client exactly that key’s access: Bearer header: the same model as the REST API, for clients that let you set headers.

Authorization: Bearer cap_fnd_live_<32 chars>   # production (keys from app.caplia.ai)
Authorization: Bearer cap_fnd_test_<32 chars>   # sandbox (developers only)

OAuth 2.1: authorisation code with PKCE and dynamic client registration. Clients that cannot send a static header, such as claude.ai custom connectors and ChatGPT, discover the flow from the 401 challenge. You then sign in on Caplia’s Connection request page by pasting your API key and clicking Authorize connection. The access token the client receives wraps that key, so revoking the key disconnects the client. Either way, the cap_fnd_* prefix is what makes the founder toolset appear. See Authentication for the company-scoped key model and how to get one.

Tools

11 founder tools, scoped to your own company. They appear automatically when you connect with a cap_fnd_* key (an investor key sees the venture toolset instead).

Read tools (require `read` scope)

Tool	What an agent asks for it
`caplia_get_my_company`	”What does Caplia have on record for my company?”
`caplia_get_my_scores`	”What’s my CRI score and what should I fix?”
`caplia_get_my_metrics`	”What traction metrics do investors see for me?”
`caplia_list_my_documents`	”What’s in my data room?”
`caplia_get_document_url`	”Download my current pitch deck.”
`caplia_list_deck_drafts`	”Show me the CRI across all my deck drafts.”
`caplia_get_deck_draft`	”What did my latest draft score?”

Write tools (require `write` scope)

Tool	What an agent asks for it
`caplia_update_my_company`	”Update my company stage and website.”
`caplia_upload_document`	”Add this financial model to my data room.”
`caplia_submit_deck_draft`	”Score this deck privately.”
`caplia_publish_deck_draft`	”Publish the winning draft as my live deck.”

Every tool resolves your company from the key - there are no company ids to pass, and the agent can’t touch any company but yours.

Connect from Claude or ChatGPT

To use Caplia from Claude on the web or from ChatGPT, add it as a custom connector and approve the connection with your key. No config files or headers are involved. The step-by-step guide, with a 1:57 video, is Connect Caplia to Claude and ChatGPT.

Connect your AI assistant

For clients you configure yourself, connect once, then drive the whole deck loop in plain English. First, get three things ready:

Get a founder key

Create a key in the founder portal from the account menu, under API Keys (see Authentication). The app gives you a cap_fnd_live_* key for your real company. Give it the write scope as well as read if you want the assistant to submit and publish decks.

Note the server URL

Production: https://mcp.venture.caplia.ai/ for cap_fnd_live_* keys, which is what the Caplia app issues. Sandbox: https://mcp-sandbox.venture.caplia.ai/ for cap_fnd_test_* keys from the staging environment, for developers only. The environments are strict: a test key is rejected by the production host and vice versa. The examples below use production.

Install Node.js, only if you use the Claude Desktop config file

Claude Desktop reaches the server through a small helper (npx mcp-remote) that needs Node.js (the LTS installer). Claude Code and Codex don’t need it - skip this step for those.

Now set up your assistant:

Using Claude on the web or ChatGPT? Add Caplia as a custom connector and sign in with your key on Caplia’s Connection request page: see Connect Caplia to Claude and ChatGPT. The tabs below send your key in a header instead.

Claude Desktop
Claude Code
Codex
Cursor / other clients

Uses Claude Desktop’s config file and sends your key in a header.

Open (or create) your Claude config file:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Paste this, with your key in place of cap_fnd_live_YOUR_KEY:

{
  "mcpServers": {
    "caplia": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.venture.caplia.ai/",
        "--header",
        "Authorization: Bearer cap_fnd_live_YOUR_KEY"
      ]
    }
  }
}

Quit Claude Desktop completely and reopen it (closing the window isn’t enough).
Open a new chat and click the tools (plug) icon - the caplia tools should be listed. Ask “What’s my CRI on Caplia?” to confirm.

Requires Node.js (step 3 above). Developers testing against the sandbox use https://mcp-sandbox.venture.caplia.ai/ with a cap_fnd_test_* key instead.

One command - no file editing:

claude mcp add --transport http caplia https://mcp.venture.caplia.ai/ \
  --header "Authorization: Bearer cap_fnd_live_YOUR_KEY"

Then run /mcp inside Claude Code (or claude mcp list in your shell) to confirm caplia connected and shows its tools. Add --scope user to make it available in every project.

Codex connects to remote MCP servers natively. It reads the key from an environment variable by name (never inline), so export it first:

export CAPLIA_API_KEY="cap_fnd_live_YOUR_KEY"   # add to ~/.zshrc to persist it

Then add the server:

codex mcp add caplia \
  --url https://mcp.venture.caplia.ai/ \
  --bearer-token-env-var CAPLIA_API_KEY

Run /mcp in the Codex TUI (or codex mcp list) to confirm. This writes a [mcp_servers.caplia] block to ~/.codex/config.toml.

Most other MCP clients need the same three things:

URL: https://mcp.venture.caplia.ai/ (or the sandbox host for test keys)
Authorization header: Bearer cap_fnd_(live|test)_<key>
(Optional) a name: caplia

In Cursor: Settings → Features → MCP → Add new MCP server, set the type to sse (streamable HTTP), then paste the URL and the Authorization header. For Windsurf and others, check your client’s MCP docs for where the config lives. Clients that support OAuth can skip the header and sign in with your key on Caplia’s Connection request page instead.

Run the deck loop from your assistant

Once connected - in Claude, Codex, or any MCP client - drive the whole deck loop in natural language. Give the assistant access to a deck tool (Canva, Google Slides, a local generator) and ask:

“Submit my pitch deck seed-deck.pdf to Caplia for private scoring. Read the recommendations, rebuild the weak slides to address them, and resubmit. Keep iterating until my CRI is at least 700, then show me the best draft before we publish it.”

The agent submits drafts, reads the private CRI and recommendations, regenerates the deck, and resubmits - looping until you’re Verified. Drafts stay private the whole time; only caplia_publish_deck_draft makes a public update.

Quick test from the terminal

# Without a key every method returns 401 plus the WWW-Authenticate challenge
curl -i -X POST https://mcp.venture.caplia.ai/ \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

# Protocol handshake with your key
curl -X POST https://mcp.venture.caplia.ai/ \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer cap_fnd_live_..." \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

# List the founder tools
curl -X POST https://mcp.venture.caplia.ai/ \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer cap_fnd_live_..." \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# Read your scores
curl -X POST https://mcp.venture.caplia.ai/ \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer cap_fnd_live_..." \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"caplia_get_my_scores","arguments":{}}}'

Troubleshooting

Symptom	Likely cause	Fix
The Connection request page rejects your key in Claude or ChatGPT	The key is revoked, mistyped, or a `cap_fnd_test_*` key on the production host	Paste the whole `cap_fnd_live_*` key, or create a new one under API Keys. See Connect Caplia to Claude and ChatGPT
The client fails to connect with `401`, or asks you to sign in	It reached the server without a key: every method, including `initialize` and `tools/list`, needs one	Re-check the `Authorization` header (or `--header` line) in your config and restart the client, or complete the OAuth sign-in
`401` / invalid key, even though the key looks right	Key and host environments don’t match	`cap_fnd_test_` keys only work on `mcp-sandbox.venture.caplia.ai`; `cap_fnd_live_` keys only on `mcp.venture.caplia.ai`
Investor tools appear instead of the founder tools	The key isn’t a `cap_fnd_*` key	Mint a founder key in the founder portal (see Authentication)
No Caplia tools in Claude Desktop after editing the config	App not fully quit, a JSON syntax error, or Node.js missing (`mcp-remote` needs it)	Validate the JSON, install Node.js, then quit Claude Desktop completely and reopen it
Deck-loop tools fail with a permissions error	Key has `read` scope only	Mint a `write`-scoped `cap_fnd_*` key

Limitations

Sandbox for testing. Developers can rehearse against the -sandbox host with a cap_fnd_test_* key from the staging environment. Keys from app.caplia.ai are live keys and work on the production host only.
No streaming responses. Each tool call is a single request-response; deck scoring is polled via caplia_get_deck_draft.
50 MB max per deck or document, base64-encoded.
JSON output only. Each tool returns raw JSON from the REST endpoint as a text content block.

Getting started

Improve your deck

Integrations

API reference

Endpoints

What you can do

Iterate your deck to 700

Understand your score

Keep your profile current

Manage your data room

Endpoints

Authentication

Tools

Read tools (require `read` scope)

Write tools (require `write` scope)

Connect from Claude or ChatGPT

Connect your AI assistant

Run the deck loop from your assistant

Quick test from the terminal

Troubleshooting

Limitations

​What you can do

Iterate your deck to 700

Understand your score

Keep your profile current

Manage your data room

​Endpoints

​Authentication

​Tools

​Read tools (require read scope)

​Write tools (require write scope)

​Connect from Claude or ChatGPT

​Connect your AI assistant

​Run the deck loop from your assistant

​Quick test from the terminal

​Troubleshooting

​Limitations

What you can do

Endpoints

Authentication

Tools

Read tools (require `read` scope)

Write tools (require `write` scope)

Connect from Claude or ChatGPT

Connect your AI assistant

Run the deck loop from your assistant

Quick test from the terminal

Troubleshooting

Limitations