Your CRM, inside Claude, ChatGPT and Cursor.
One URL turns your workspace into tools any AI client can use. Records, pipelines, sequences, workflows, conversations and meeting notes, all reachable in plain language, all scoped to the workspace you signed into.
- One URL, no API key
- 95+ tools, discovered automatically
Claude · Vetta MCP
What people build
Your CRM as a tool other AI can use.
Connected clients discover the whole catalog on their own. You describe the outcome; the client picks the tools.
Run the pipeline from chat
“Find opportunities in Negotiation with no activity in two weeks, and create a follow-up task for each owner.” It reads, decides and writes in one turn.
Operate outreach
“Enroll everyone from yesterday’s import with a verified email into the Q3 sequence, and pause anyone who already replied.”
Build automations by describing them
Your assistant can create a workflow, set the trigger, add the steps, activate it and read the first run, all through tools.
Brief before you write
Meeting notes, email threads and WhatsApp history become context the assistant reads before drafting a single line.
Reshape the schema
Add a custom field, fix its options, or discover what a workspace already has, without clicking through settings.
Work from the editor you live in
Cursor, Cline, Continue and Zed speak MCP too, so CRM data sits next to the code you are shipping.
Deliberately not exposed: raw HTTP requests and the sandboxed code interpreter, which stay inside Vetta’s own agents.
01Chat-driven CRM
Ask for the outcome, not the query
One sentence can span three objects: find the stalled deals, check the last activity on each, then write a task for every owner. The assistant chains the reads and the writes itself, and everything lands in Vetta attributed to you.
- Search and filter any entity, standard or custom
- Create, update and delete records
- Discover fields, types and options on the fly
Jonas Weber
Clara Vidal
Tomás Ferrer02Build, not just read
It can wire up the automation too
Workflows and sequences are tools like any other. Your assistant can create a workflow, set the trigger, add each step, publish the version and read the first run, then enroll or pause the right people in a campaign.
- Full workflow lifecycle: build, publish, run, inspect
- Edit sequence steps and manage enrollments
- Preview a step output before wiring the next one
Hannah Koch03Context
It reads the conversation before it writes one
Synced email, WhatsApp and LinkedIn threads plus AI meeting notes are all readable, so the assistant knows what was actually said before it drafts anything. Then it can send on the right channel, or just save a draft for you.
- Conversations across all three channels
- Meeting summaries, transcripts and action items
- Send, or save a draft and decide later
04Scope
Signed in, not handed a secret
There is no key to paste or rotate. You sign in, and every call runs in the context of that workspace: a tool can never reach another one. Read-only tools are annotated so your client can treat them as safe.
- Standard MCP OAuth, scoped to one workspace
- Read-only tools annotated for the client
- Bearer-token API keys for headless use only
- 44
- tools across six domains of your workspace
- 1 URL
- to connect, with zero API keys to manage
- Any
- MCP client: Claude, ChatGPT, Cursor, Zed
On the route
Vetta MCP works at every stop. From the first signal to the signed deal.
Questions
Vetta MCP, explained
What is MCP?
The Model Context Protocol is an open standard for connecting an AI client to an external system. Vetta ships a native MCP server, so any MCP-speaking client can read and write your workspace without a custom integration.
Which clients can connect?
Claude on claude.ai and Claude Desktop, Claude Code, ChatGPT, Cursor, Cline, Continue, Zed, and anything else that speaks MCP. In Claude and ChatGPT you add it as a custom connector; in editors you add it to the MCP config.
Do I need an API key?
No. Connecting is one URL plus a normal Vetta sign-in, using standard MCP OAuth. API keys are only for headless use: scripts, CI or agents with no browser to sign in with, which can pass a key as a bearer token instead.
What can the AI actually do?
Forty-four tools across records and custom fields, pipelines, sequences, workflows, messaging on email, WhatsApp and LinkedIn, and AI meeting notes. The client discovers the full catalog on connection, so it stays current as tools are added.
Is it safe to give an AI client write access?
Every call runs in the context of the workspace you signed in with, and a tool can never reach another workspace. Read-only tools are annotated so clients can treat them as safe, and raw HTTP requests and the sandboxed code interpreter are deliberately not exposed.
Why can my client not connect?
MCP is enabled per workspace, so check that it is on for your plan. The same setup snippet lives in the app under Settings, AI, Set up MCP.
How does this relate to Claude Skills?
They compose. MCP gives the assistant tools it can execute. Claude Skills give it knowledge: the conventions, formats and gotchas of the Vetta API, so it uses those tools correctly on the first try. In Claude Code, connect the server and install the skills.
Vetta MCP
Give your AI tools a system of record.
One URL, a normal sign-in, and 95+ tools your assistant discovers on its own.
One URL, no API key · 95+ tools · Any MCP client