Connect MailerLogic MCP to Claude and Claude Code
MailerLogic MCP lets you securely connect Claude and Claude Code to your MailerLogic account. Once connected, Claude can help you manage contacts, send test emails, view templates, and access analytics using approved MailerLogic tools, all without leaving your chat or coding workflow.
Step 1: Get the MCP Server URL
Go to Integrations → Apps. Open the 'MailerLogic MCP' card and copy the 'MCP Server URL'. It should look like:
https://mcp.mailerlogic.com/mcp
Step 2: Generate a token (Claude Code only)
On the MailerLogic MCP card, click 'View Docs'.
Step 3: Generate the Token
Click 'Generate token'.
Step 4: Copy and Save the Token
Copy the token immediately. It is displayed only once, so store it securely in a password manager.
Step 5: Open Claude Connectors
Open Claude → Settings → Connectors. Choose 'Add custom connector'.
Step 6: Add the MCP Server
Enter a 'Name', then paste the MailerLogic MCP Server URL into the 'Remote MCP server' field.
Step 7: Authorize the Connection
Click 'Add'. Claude opens a MailerLogic authorization flow. Sign in if prompted, review the requested access, and click 'Authorize'.
Complete the connection, then choose which MailerLogic tools Claude is allowed to access.
Add MailerLogic from Settings → Connectors. Do not add the remote MailerLogic MCP URL to
claude_desktop_config.json. That configuration file is only for local MCP servers and desktop extensions, not remote OAuth connectors.
Step 8: Connect Claude Code
Claude Code connects to remote MCP servers using the command line. The exact command or workflow may vary depending on your Claude Code version, so refer to the latest Claude Code MCP documentation if your interface looks different.
Use the MailerLogic MCP server URL from Step 3.
https://mcp.mailerlogic.com/mcp
-
If Claude Code offers OAuth, choose it and complete the browser authorization flow.
If Claude Code asks for a header or access token instead, use the token from Step 4.
claude mcp add --transport http mailerlogic https://mcp.mailerlogic.com/mcp \ --header "Authorization: Bearer YOUR_MCP_TOKEN"Replace
YOUR_MCP_TOKENwith the token shown in MailerLogic.
Step 9: Test the Connection
After connecting, try prompts like:
- "Search MailerLogic contacts for yasmin@example.com."
- "Create a contact for Alex Rivera with email alex@example.com."
- "Add the tag webinar-lead to alex@example.com."
- "Show me recent email events for the last 7 days."
- "Summarize my MailerLogic analytics for this week."
- "List available email templates."
Claude may ask you to approve tool use before it takes action; review each request before approving.
Step 10: Manage Access
Manage Claude's access from MailerLogic → Integrations → Apps → MailerLogic MCP:
- Rotate token — creates a new token and invalidates the old one.
- Revoke — disconnects assistants using the current token.
- Copy MCP URL — copies the server URL for reconnecting.
If you rotate or revoke the token, Claude may need to reconnect.
Troubleshooting
Claude shows a 404 page.
Make sure the server URL ends with /mcp:
https://mcp.mailerlogic.com/mcp
The connector could not be loaded
Verify that:
- The MCP Server URL is correct.
- MCP is enabled for your MailerLogic account.
- Your subscription plan includes MCP access.
Claude asks for an OAuth Client ID or Client Secret
Leave both fields blank unless MailerLogic Support has specifically provided values.
Claude says "Unauthorized" or "Access denied"
Generate a new MCP token in MailerLogic and reconnect.
Claude can read data but cannot perform certain actions
Some actions are intentionally restricted for security reasons, including:
- Sending campaigns to an entire audience
- Making billing changes
- Performing destructive bulk operations
Security tips
- Treat your MCP token like a password.
- Store your token in a secure password manager.
- Only connect MailerLogic to trusted AI tools.
- Review Claude's requested actions before approving them.
- Never share your MCP token in chat messages, screenshots, or public repositories.
- Revoke access immediately if you suspect your token has been exposed or you no longer use the connection.