Use Tantra from your MCP-compatible AI client.
Connect Tantra to Claude, Claude Code, Cursor, or another MCP client and operate supported campaigns, contacts, email, inbox, webinar, webhook, and settings workflows in natural language.
Requires a dedicated Tantra API key.
What you get
Dozens of registered tools
Call a broad tool set covering both campaign paths, from campaigns to inbox replies.
Calendar campaigns and sequences
Operate calendar campaign lifecycle and reporting, plus sequence campaigns, steps, enrollments, and analytics.
Contacts, inbox, and webinars
Work with contacts and lists, inbox threads and replies, and Zoom or WebinarGeek webinar reports.
Webhooks and account tools
Manage outbound webhooks, templates, senders, settings, suppression, dashboard, and identity tools.
Two transports
Run the server over local stdio or a hosted Streamable HTTP transport.
API-key authentication
Authenticate with an API key, with per-session tenant binding on the hosted transport.
How it works
- Step 1
Create a dedicated API key
- Step 2
Choose hosted HTTP or local stdio
- Step 3
Add the client configuration
- Step 4
Call whoami
- Step 5
Use tools
Supported actions and data
Tantra can do
- Operate the registered tool set from any MCP-compatible client
- Bind a session to your Tantra account with an API key
Tantra receives
- Tool call results returned to your MCP client
Requirements and permissions
A dedicated Tantra API key
An MCP-compatible client (Claude, Claude Code, Cursor, or similar)
Good to know
- Your MCP client lists the current tools once it connects.
- MCP exposes a defined tool set, not every control in the Tantra UI.
- API keys are account-level, not scope-enforced.
- An MCP client configuration holds a live API key, so treat it like any other credential and revoke the key if it is exposed.
Frequently asked questions
How many tools does the MCP server expose?
- Dozens, covering both the calendar and sequence campaign paths. The set changes as tools are added, so connect a client and list them rather than relying on a number quoted here.
Does MCP expose every control in the Tantra UI?
- No. It exposes a defined tool set, not every control available in the web app.
Are MCP requests scoped to specific permissions?
- No. Like REST API keys, MCP authentication is account-level and not scope-enforced.
Related integrations
REST API
Use revocable account-level keys to automate supported Tantra API operations.
- Operate campaigns, contacts, webhooks, and related workflows over HTTPS
- Authenticate requests with an X-API-Key header
Outbound Webhooks
POST calendar, email, LinkedIn, WhatsApp, and Telegram events to your HTTPS endpoint.
- POST calendar, email, LinkedIn, WhatsApp, and Telegram events to your endpoint
- Retry delivery and keep a delivery history per attempt
Create an API key.
Operate supported Tantra workflows from Claude, Cursor, and other MCP clients.