Meta Tech ProviderThe ThinnestAI MCP Server: Build and Run Voice and WhatsApp Agents from Claude Code, Cursor or VS Code
The short version
ThinnestAI is now an MCP server. Add it to Claude Code, Cursor or VS Code with one of your API keys, and your coding assistant can run your workspace: create agents, write their instructions, connect them to your own systems, read conversations and call transcripts, and build dashboards on top.
The address is https://app.thinnest.ai/api/v1/mcp. The assistant works through the same API your own code would use, so it can do exactly what its key can do — and nothing more.
What you can ask for
- "Create a support agent for our clinic that answers in Hindi and English." The assistant creates the agent, writes its instructions and sets its languages.
- "Connect it to our appointments API." It adds an action — an HTTPS endpoint of yours the agent calls mid-conversation — tests it, and asks you before switching it on.
- "Which customers asked about refunds this week?" It reads the conversations and summarises them.
- "Call these five leads tomorrow at 11." It prepares the calls and asks for your approval before any phone rings.
- "Build me a dashboard of yesterday's calls." It writes the code against the API and sets up the webhooks.
Test the agent without leaving the editor
The step that usually sends you back to a browser is checking the change worked. The test_chat tool talks to your real agent — same instructions, model, knowledge and actions — and returns its reply along with every tool it used and what went in and out.
In a test chat, anything that would phone, message, email or send a code to a person, or change a calendar booking, is switched off. The agent says what it would have done instead — "I would schedule a callback for 5pm" — so you can see the behaviour without anyone being contacted.
Nothing reaches a customer without your yes
Every tool that messages a customer, places a call, deletes something, or decides where your customers' data is sent asks for your approval first. Each one is marked destructive so your client asks you; and because a client can be set to auto-approve, the tool itself refuses to run unless the assistant confirms you said yes.
Sending and calling tools also need a retry key, so an assistant that retries after a timeout cannot message the same person twice.
Choose what the key can do
| Key | The assistant can |
|---|---|
| Build | Build agents, connect your API, manage contacts and webhooks, read everything and test-chat — but not message anyone or place calls |
| Read-only | Read conversations, calls, contacts and settings |
| Full access | Everything, including sending and calling — each still asking for your approval |
The MCP server only shows the assistant the tools its key may use. Start with a Build key.
Connect in one line
In Claude Code:
claude mcp add --transport http thinnestai https://app.thinnest.ai/api/v1/mcp \
--header "Authorization: Bearer ta_live_YOUR_KEY"Cursor, VS Code and Claude Desktop take a short config — the console shows each one ready to copy under Settings → API keys → Connect an AI assistant.
What works today
Claude Code, Cursor, VS Code, and Claude Desktop or Windsurf through a small bridge. Connectors inside claude.ai and ChatGPT sign in with OAuth, which is not available yet.