MCP Connector

What the MCP connector does

The MCP connector adds your Tavnit organization as a set of tools inside an AI assistant. Once connected, you describe what you need in plain language and the assistant designs and configures it in your live account: flows, cleaning rules, buckets, pipelines, integrations.

MCP (Model Context Protocol) is the open standard that lets AI assistants call external tools. Tavnit runs an MCP server at https://mcp.tavnit.io/mcp. The connector signs you in with your Tavnit account (OAuth 2.1), so there is no key or URL to copy: the assistant acts as you, in the organization you pick, with your role. It works with claude.ai (Pro and above), Claude Code, Claude Desktop, Cursor, ChatGPT (paid plans) and any other client that supports remote MCP servers with OAuth.

For what the connector is for, and how it compares to pasting a file into a chat, see the MCP connector overview.

Available to every organization

MCP access is on for every Tavnit organization. If the AI apps card is missing from your Integrations page, an administrator has switched it off for your organization; contact support to have it restored.

Before you start

You need a Tavnit account that belongs to at least one organization, and an MCP client. That is all: the connection is approved with your sign-in, not with a key.

Requirement	Where it comes from
A Tavnit account	The same email and password (or Google sign-in) you use for the app. The consent page asks you to sign in when you are not already.
An organization	You pick one when you approve the connection. Only organizations you belong to, with MCP access on, are offered.
An MCP client	claude.ai on a Pro plan or above, Claude Code, Claude Desktop, Cursor, ChatGPT on a paid plan, or any client that supports remote MCP servers with OAuth.
Your role	The assistant inherits your role in the organization you picked, so it can do only what you can do. See user roles.

Connect claude.ai

Add Tavnit as a connector and approve it with your account. There is nothing to install and no configuration file to edit.

1Open Integrations in the Tavnit sidebar. The AI apps card shows the server URL and an Add to Claude button.
2Select Add to Claude, or in claude.ai go to Settings → Connectors → Add custom connector and enter the server URL below. Leave the OAuth client id and secret empty.
3Select Connect. A Tavnit page opens: sign in if you are not already, choose the organization the assistant may work in, and approve.
4Open a new chat and ask the assistant which Tavnit tools it has. If it lists them, the connector is live.

text

https://mcp.tavnit.io/mcp

Connect Cursor, Claude Code, ChatGPT or another client

Every client takes the same server URL and runs the same sign-in. Add it as a remote (URL) server, not a command-based one: there is no local process to run.

Client	How
Cursor	Select Add to Cursor on the Integrations page, or add `{"mcpServers":{"tavnit":{"url":"https://mcp.tavnit.io/mcp"}}}` to `~/.cursor/mcp.json`. Then open Settings → Tools & MCP and select Login on the Tavnit entry.
Claude Code	Run `claude mcp add --transport http tavnit https://mcp.tavnit.io/mcp`, then `/mcp` → Tavnit → Authenticate.
Claude Desktop	Settings → Connectors → Add custom connector with the server URL, then Connect.
ChatGPT	Settings → Connectors → Add custom connector (developer mode may need to be on). Enter the server URL, choose OAuth and leave the client fields empty, then Connect.

One sign-in per client

Each client gets its own connection, approved separately. They all act as you, in the organization you picked for each one, and each can be revoked on its own.

What your assistant can do

Through the connector, the assistant designs, configures and integrates: it creates flows and their fields, adds cleaning rules, sets up buckets, inspectors, fillers, subjects and pipelines, and wires results to webhooks, email and no-code tools. It also reads your runs and results to validate a design.

Processing itself stays where it is: documents are uploaded and runs started in the Tavnit app, by email or through the API, and reviews are approved in the app. The connector never spends credits.

Your data, your organization

A connection reaches only the organization you picked when you approved it. To work with another organization, disconnect the app and connect it again: you will be asked to pick again.

Managing and revoking connections

The Connected AI apps list on the Integrations page shows every app you approved, when, and for which organization. Revoking one cuts its access at once.

Action	What happens
Revoke	The app's access ends immediately. Its next request fails until you connect it again from the app, which asks you to sign in and pick an organization.
Leave an organization	Connections pointing at that organization stop working on their own.
MCP access switched off	Every connection to that organization stops working until it is switched on again.

Revoking is immediate and there is no undo: the app has to be connected again. Do it when you can reconnect straight away, or when you mean to cut access for good.

Security

Connections are standard OAuth 2.1: short-lived tokens the client refreshes on its own, approved on a page you control, revocable at any time.

Nothing to copy or store: there is no credential to paste into a client, so there is nothing to leak in a ticket, a chat or a screenshot.
The assistant acts with your role in the organization you picked, and can never do more than you can in the app.
Processing, reviews and credits stay in the app; the connector designs and configures only.
Your API key is separate. Scripts and automations keep using it; the connector does not.

Troubleshooting

Most connector problems are one of four things: the connection was revoked, your membership or role changed, MCP access is off, or the client holds an old connection to another organization.

Symptom	Cause	Fix
No AI apps card on Integrations	MCP access is switched off for your organization.	Contact support to have it turned on.
The consent page says none of your organizations has MCP access	You belong only to organizations where it is off.	Ask the organization's owner or support to enable it.
The assistant stopped seeing Tavnit	The connection was revoked, or your membership changed.	Remove the connector in the client and add it again.
The assistant sees the wrong data	You picked a different organization when you approved.	Revoke the connection on Integrations, reconnect and pick the right organization.
The assistant cannot perform an action	Your role does not allow it.	Check your role before assuming a connector fault.

When to use the connector instead of the API

Use the connector for conversational work: designing a flow, adding a rule, checking results, wiring an integration. Use the REST API for anything scheduled, high-volume or embedded in another system, where you need explicit error handling and retries.

Situation	Use
Design a flow and its cleaning rules by describing them	MCP connector
Check why last week's runs failed	MCP connector
Every invoice from a vendor portal, nightly	REST API or an email trigger
Your own product needs the extracted data	REST API plus webhooks