Integrations · Developer

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.
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
- 1Create a dedicated API key
- 2Choose hosted HTTP or local stdio
- 3Add the client configuration
- 4Call whoami
- 5Use 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.