1. Use the MailKatana MCP server URL

Use the Streamable HTTP server URL:
Legacy clients that explicitly require the older SSE transport can continue to use:
If you request either URL without the Authorization header, expect a 401. That means the server is live but the request has not authenticated yet.

2. Send the API key as a Bearer token

Use the same workspace API key that you use for the REST API.
Different clients use different config shapes, but the important parts stay the same:
  • transport is Streamable HTTP
  • URL points directly at /mcp
  • auth lives in the Authorization header
  • auth must be present on every transport request
For Codex-style configuration, place the API key in an environment variable rather than the configuration file:

3. Verify the connection

If auth and transport negotiation are correct, you should get a JSON-RPC initialize response rather than a 401. If you omit the header and get a 401, that still confirms the route exists.

4. Call a simple tool first

Start with one of these tools:
  • list_templates
  • list_mailing_lists
  • list_contacts
Then move to mutating tools such as create_contact, send_event, or send_email — or, to run a marketing campaign, create_campaign followed by send_campaign.