Connecting your AI Agent to QuickMail MCP 🤖

QuickMail's MCP lets you connect your QuickMail account to AI assistants like Claude and ChatGPT. Once connected, you can use your AI assistant to get insights from your campaigns, manage leads, create campaigns, and perform other QuickMail tasks without writing code.

In this article

• How does it work
• What can you do with QuickMail's MCP
• IMPORTANT: Before you start
• How to connect QuickMail's MCP to Claude
• How to connect QuickMail's MCP to ChatGPT
• Troubleshooting

How does it work

QuickMail's MCP connects your AI assistant to your QuickMail account, allowing it to retrieve information and perform supported actions through QuickMail's API.

Once connected, you can simply tell your AI assistant what you need. It can then fetch the relevant data or carry out the action for you, without requiring you to write code.

For example, you can ask: "Show me the performance of my Q4 Outreach campaign."

Your AI assistant can retrieve the campaign data from QuickMail and present the results to you.

What can you do with QuickMail's MCP

With QuickMail connected, your AI assistant can help you work with your campaigns and leads, answer questions about your data, and perform specific campaign-related actions. Everything available in QuickMail's API is also available through MCP.

Here are some of the things you can do:

Campaigns

• Get campaign statistics, such as opens, clicks, replies, and bounces
• Analyze your campaign data and ask questions about your outreach
• Get campaign IDs, names, and URLs
• Create, clone, and rename campaigns
• Create and update email, wait, and LinkedIn steps
• Add email variations to your steps
• Update campaign send times and email verification settings

Leads

• Create and delete leads
• Add, cancel, and remove leads in campaigns
• Search for leads by name, email, phone, or LinkedIn ID
• Filter leads by tag or campaign
• See how many leads in a campaign are available, active, completed, or have run into an error
• Mark leads as Do Not Contact (add them to your exclude list)
• Create tags and assign them to leads
• Create custom properties and set their values on leads

Email accounts

• Get email account IDs and sender account information
• Assign and unassign email accounts to and from campaigns
• Set custom tracking domains
• Change an email account’s sender name
• Set an email account’s daily sending limit and recovery period
• Set sending groups for Deliverability AI

Opportunities

• List and view your opportunities
• Reply to an opportunity

Agency and workspaces

• Get agency information, including name, ID, and URL
• Get workspace IDs, names, and URLs
• Include or exclude specific workspaces when searching

And more

• Retrieve other data and perform other actions supported by the QuickMail API

⚠️ Before you start

You'll need:

• An AI app that supports remote MCP servers with OAuth sign-in.
• A paid AI subscription may be required, depending on the app.
• Your QuickMail login and access to the organization you want to connect
• API access enabled for that QuickMail organization (Not available for accounts on Starter Plan)

You'll sign in with your regular QuickMail account, so there's no need to create or paste an API key.

How to connect QuickMail's MCP to Claude

Step 1. Go to Claude Settings → Connectors → +Add → Add custom connector

Step 2. Enter the following details and click 'Continue'

• Name: QuickMail
• Transport, if asked: Streamable HTTP
• Server URL:https://api.quickmail.com/mcp

Step. 3 Follow the on-screen instructions. Select the following settings and then click 'Add'

• Authentication: Sign in now
• OAuth client: Register Automatically

Step. 4 Connect your QuickMail account via OAuth sign-in. Make sure to select the correct organization (if you're managing multiple organizations) that you'd like to connect.

Step. 5 You'll be redirected to your Claude Settings. To confirm whether you've successfully connected, you'll see QuickMail in the list of connectors.

Step. 6 You can now ask your AI to work with your QuickMail data.

How to connect QuickMail's MCP to ChatGPT

Step 1. Go to ChatGPT Settings → Plugins → Add → Add MCP server

Step 2. Enter the following details and click 'Save'

• Name: QuickMail
• Transport, if asked: Streamable HTTP
• Server URL: https://api.quickmail.com/mcp

Step 3. You'll be redirected to ChatGPT's Plugins page. Go to the MCPs tab and Click 'Authenticate' for QuickMail

Step 4. Connect your QuickMail account via OAuth sign-in. Make sure to select the correct organization (if you're managing multiple organizations) that you'd like to connect.

Step. 5 You'll be redirected to ChatGPT's Plugins page. Make sure that QuickMail is listed under MCP servers and is enabled.

Step. 6 You can now ask your AI to work with your QuickMail data.

Troubleshooting

The connection does not start

Check that the server URL is exactly https://api.quickmail.com/mcp and that your app supports remote MCP with OAuth. Use OAuth sign-in rather than an API key or manual authorization header.

Alternatively, if you're using the Free version of your AI app, check that your plan supports custom MCP connections. Custom MCP access may not be available on the Free plan.

I opened the URL and got an error

The server URL is for your AI app’s connector settings. It is not a web page. Paste it into the connector setup to begin.

My organization is missing or access is denied

Check that you signed in to the correct QuickMail account and still have access to the organization. Your organization must also have API access enabled.

I can read data but cannot make changes

Check your workspace permissions with your organization administrator. Read-only guest access does not allow updates or deletions.

The connection stopped working

Reconnect to sign in again. If that does not resolve it, check whether your QuickMail account, organization, or workspace access has changed.

I get a “Too many requests” error

Wait briefly, then try again. MCP uses the same organization request limit as the QuickMail API.

For available API fields and operations, see the API v2 documentation.