Using Kapitable from an AI assistant

Overview

You can connect an AI assistant to Kapitable and ask about your projects in plain language: "What is still missing before we can close the management round?", "Who do I need to chase today?", "How did the BidCo cap table change after the last wave?" Four assistants are supported today: Claude, from Anthropic, ChatGPT and Codex, from OpenAI, and Mistral Vibe, from Mistral AI.

The connection works through Kapitable's MCP server. MCP, short for Model Context Protocol, is an open standard that lets an AI assistant plug into other software safely. Think of it as a power socket: the assistant has the plug, Kapitable provides the socket, and the standard makes sure the two fit. The assistant never gets a copy of your data to keep; it asks Kapitable for what it needs to answer each question, with your own login.

What you'll learn

• What an assistant can do with Kapitable, and what it cannot

• How a Project Admin turns on AI assistant access for a project

• The difference between reading and updates

• How to add Kapitable in Claude, ChatGPT, Codex or Mistral Vibe

What you can do with it

Ask and understand, from your own projects:

• the closing status of a round: what is missing, who must act, whether it can close;

• who to chase, for what, and when they were last reminded;

• a cap table, at a past date or compared between two points in time;

• a person across the deals you can see: holdings, KYC status, documents;

• a review of imported data: missing contacts, likely duplicates, companies without a registration number;

• how to do something in Kapitable, answered from this Help Centre.

Work with your other tools. Your assistant can turn an answer into a spreadsheet or a draft email, using the other tools you have connected to it. Kapitable itself only sends its own workflow emails (invitations, requests, reminders, signature envelopes).

Make updates, if a Project Admin allows them: record transactions, add subscribers, send reminders and more. The assistant always asks you to confirm before it changes anything.

What it cannot do

• See more than you can. The assistant works with your login: it sees exactly what your role lets you see in Kapitable, and nothing else.

• See a project that has not turned it on. Each project's admins decide; until they do, no assistant can reach that project at all.

• Read identity or bank details. ID numbers, addresses, dates of birth, identity documents and IBANs stay in Kapitable. The assistant can see whether a KYC check is complete or expired, not what it contains.

• Use the investor portal. Shareholders and managers using the portal cannot use an AI assistant yet.

Step 1: turn on AI assistant access for the project

A Project Admin or Org Admin does this once per project.

1. Open the project, then Project Settings, then AI Assistant.

2. Switch on Use this project from an AI assistant.

3. Read the summary and, if you wish, Read the full terms. Tick the box to accept them on behalf of the project.

4. Click Turn on.

Access is now on, for reading only. Every member of the project can use their own assistant on it, within their own role. Other members see the setting but cannot change it.

Reading and updates

Updates through an assistant is off until an admin switches it on and confirms with Allow updates. Even then, a member can only update what their role allows: a Viewer stays read-only.

Every switch is recorded in the project's Audit Trail, and every update made through an assistant is marked via AI assistant next to the person who made it.

Step 2: add Kapitable in your assistant

Each member does this once, in their own account. The AI Assistant page shows the values to copy, each with a copy button.

In Claude

1. In Claude, open Settings, then Connectors.

2. Click Add, then choose Custom connector.

3. Enter the name: Kapitable.

4. Enter the MCP server URL shown on the AI Assistant page.

5. Click Add, then Connect, and sign in with your Kapitable login.

In ChatGPT

ChatGPT takes more steps than the other assistants: an admin of your ChatGPT workspace adds Kapitable as a custom app once, then each member connects their own Kapitable login. It needs a ChatGPT Business, Enterprise or Edu workspace, and works on chatgpt.com in a browser, not in the mobile app.

Part A: a ChatGPT workspace admin adds Kapitable (once for the workspace)

1. On chatgpt.com, open your profile menu, then Workspace settings.

2. In the left menu, under Plugins, click Apps.

3. Click Create. If ChatGPT asks you to turn on developer mode, accept: it applies to your own account only.

4. Fill in the form. Name: Kapitable. Description (optional): for example Kapitable projects, cap tables and closings. Connection: leave Server URL selected and enter the MCP server URL shown on the AI Assistant page. Authentication: OAuth.

5. Open Advanced OAuth settings and check two things. Registration method shows Client Identifier Metadata Document (CIMD) — leave it, and ignore the warning that DCR is unavailable, which is expected. Under Default scopes, both kapitable/mcp and offline_access are ticked — without offline_access, members would have to sign in again every hour.

6. Tick I understand and want to continue, then click Create. The app appears under Drafts, marked DEV. At this stage only you can use it.

7. To make it available to the rest of the workspace, click Publish. On a Business workspace a published app cannot be edited: to change it later, create it again.

Part B: each member connects their Kapitable login

1. In ChatGPT, open Plugins (in the sidebar, or Settings, then Plugins) and click Kapitable under Installed.

2. Click Connect. Your browser opens Kapitable's page, Connect ChatGPT to Kapitable.

3. Sign in with your Kapitable login. Back in ChatGPT, your account appears under Connected accounts.

4. Click Try in chat, or in any new chat pick Kapitable from the + menu or type @Kapitable.

When Kapitable adds new capabilities, ChatGPT keeps the list it saw when the app was created. A workspace admin recreates the app to pick them up.

In Codex

1. In the ChatGPT app, open Settings, then Plugins.

2. Click Add, then choose Add MCP server.

3. Enter the name: Kapitable, and the MCP server URL shown on the AI Assistant page. Save.

4. In the MCPs tab, click Authenticate next to Kapitable. Your browser opens Kapitable's sign-in page.

5. Sign in with your Kapitable login straight away, in the tab Codex opened. When the browser says Authentication complete, close it and go back to Codex.

If the browser says it cannot reach 127.0.0.1, Codex stopped waiting before you signed in. Click Authenticate again and sign in in the new tab.

In Mistral Vibe

1. In Mistral Vibe, switch to Work, then open Context, then Connectors.

2. Click Add connector, then add a custom connector.

3. Enter the connector name: Kapitable, and the server URL shown on the AI Assistant page.

4. Leave Authentication on Auto-detect: Vibe finds Kapitable's sign-in by itself. Click Add connector.

5. When your browser opens Kapitable's page, sign in with your Kapitable login. Back in Vibe, the connection shows as Valid.

Each Kapitable tool starts on Ask: Vibe asks you before it uses one. You can change that tool by tool on the connector's page in Connectors.

Only an admin of your Mistral workspace can add a connector. On a Free or Pro plan, you are the admin of your own workspace.

Step 3: ask

Start a new conversation and ask about your project by name, for example:

• "What is still missing before we can close the management round on Martin Industries?"

• "List the investors who have not paid yet."

• "Show me the Martin Bidco cap table as it was at the end of June."

If the assistant says it cannot find a project, check that its admins have turned on AI assistant access, and that you are a member of it.

Turning it off

An admin can switch Use this project from an AI assistant off at any time and confirm with Turn off. Assistants lose access to the project from their next request; members' connections stay in place for the projects that remain on. Switching updates off works the same way and leaves reading on.

Related

• A1.4 — Roles and what each can see · an assistant always works within your role

• A2.6 — Access control in practice · who can change project settings