Connect table to your AI client with MCP

What MCP does

MCP, or Model Context Protocol, is a standard way for AI clients to connect to tools and data from other apps. table's MCP server lets compatible AI clients request access to your table account and use approved table tools.

The MCP server is hosted separately from the main app and uses its own authorization flow. This keeps the MCP boundary explicit.

MCP server URL

Use this production remote MCP server URL when adding table to a compatible MCP client:

• Add this as a remote MCP server.
• Do not add it as a local or desktop MCP server.
• If table gives you a different production MCP URL, use that URL instead.

When to use MCP

Use MCP if you want to:

• Save relationship context from an AI client into table
• Create or update contacts from explicit contact data
• Let an assistant help maintain your CRM without giving it broad database access
• Build workflows that start outside table but end in your table account

Set up Claude

Use these steps to connect table from Claude. If table is not listed in the Claude Connectors Directory yet, add it as a custom connector.

1. 1Open Claude.
2. 2Go to Settings > Connectors.
3. 3Add a custom connector.
4. 4Choose remote MCP server.
5. 5Enter the table MCP server URL.
6. 6Start the authorization flow.
7. 7Sign in to table if prompted.
8. 8Review the client name and redirect details.
9. 9Approve only if the client looks correct.
10. 10Return to Claude and test the connection.

How authorization works

When an MCP client requests access, table shows an authorization screen. The screen identifies the client and asks you to approve or cancel.

If you are not signed in, table asks you to sign in before authorization can continue.

Approving a client allows that MCP client to use the table MCP server according to the tools and access currently available. You should only approve clients you recognize.

Connect an MCP client

The exact setup depends on the client. For clients other than Claude, the flow is usually:

1. 1Open your MCP-compatible client.
2. 2Add a remote MCP server.
3. 3Enter the table MCP server URL.
4. 4Start the authorization flow from the client.
5. 5Sign in to table if prompted.
6. 6Review the client name and redirect details.
7. 7Approve only if the client looks correct.
8. 8Return to the client and test the connection.

Data access

The current MCP surface is intentionally narrow.

The connector can create or update one contact from explicit contact data provided by the MCP client. It may write contact fields such as name, email, phone, organization, job title, location, birthday, and status.

• It does not provide raw database access.
• It does not let MCP clients browse all table data.
• It uses the authenticated table user from OAuth, not a user ID supplied by the MCP client.
• The current MCP surface writes contact data. If read tools are added later, this section should be updated.

Usage examples

After the connection is approved, try prompts like:

• Save this person as a contact in table: Ada Lovelace, ada@example.com, mathematician.
• Update my contact for Jane Doe with her new job title: VP Sales at Acme.
• Add this founder I just met to table with their email, company, and notes.
• Create a contact from this email signature.
• Save this investor as a contact with their firm and location.

Security model

• MCP clients must authenticate.
• table uses the authenticated OAuth user, not a user ID supplied by the MCP client.
• table validates tool input before writing contact data.
• MCP tools do not expose raw database rows.
• Errors are kept stable and bounded.
• table avoids logging personal data such as names, emails, phone numbers, organizations, prompts, tokens, and provider payloads.

Privacy and support

Privacy policy: https://www.usetable.ai/privacy.

Support: support@usetable.ai.

Revoke access for clients you no longer use or do not recognize.

Troubleshooting

• I do not see table in Claude Connectors: add table as a custom connector if it is not listed in the directory yet.
• Authorization opens but does not complete: disconnect and reconnect table, then start the authorization flow from Claude again.
• The client name or redirect URL looks unfamiliar: cancel authorization and contact support.
• Tool call fails: check that your table account is active and try reconnecting.
• Invalid authorization request: start the authorization flow from your MCP client.
• Unknown client: cancel the request if the client name or redirect URL is not expected.
• Approved client cannot call tools: disconnect and reconnect the MCP server in the client.
• Unrecognized client: cancel authorization and do not approve the request.