Skip to main content
InstantCampaign runs a Model Context Protocol (MCP) server. An MCP-capable AI assistant can use it to look up campaign results, check a template before a transactional send, write copy in your brand voice or draft a campaign, all inside your workspace.

What the assistant can do

The assistant cannot send email or start anything. Campaigns created through MCP wait for someone to approve the plan in the app, and journeys are created as drafts that never activate by themselves.

Privacy

MCP clients pass tool results to their own AI models, so every result goes through the same privacy filter as the in-app assistant. Contact tools return aggregates, statuses and ids, never lists of people. Every output passes a redaction layer that removes email addresses, names, phone numbers and postal addresses. For example, check_contact_status looks up an address you already have but never returns it.

Connect

1

Create a key for the assistant

In Settings → Developers → API Keys, click Create New Key. Name it after the assistant, and under Permissions tick only AI assistant (MCP). That key can then use the MCP server but not the rest of the API. See API keys.
2

Add the server to your client

Configure an MCP server with the Streamable HTTP transport:
  • URL: https://instantcampaign.ai/api/mcp
  • Header: Authorization: Bearer ic_your_key_here
For example, in Claude Code:
3

Try it

Ask the assistant something like “How did my last three campaigns perform?” It should call list_campaigns and get_campaign_performance.

Limits

  • Rate limit: 60 requests per minute per workspace. Beyond that the server answers 429.
  • Plan quotas: tools count against your plan’s monthly quotas, as they do in the app. create_campaign counts against campaign generations, generate_copy and create_journey_from_brief use AI text generations, generate_image uses AI image generations, and create_template_draft and duplicate_template count as templates. When a quota is used up, the tool returns an error saying so.
  • Transport: the server answers each request with plain JSON. It does not open server-initiated streams and issues no session id. Clients that support Streamable HTTP work as is.

Seeing what the assistant did

Every MCP call is recorded in Settings → Developers → API log under the /api/mcp path, with the tool call as the request body. See API request log.

Troubleshooting