Connect InboxAlly to Claude, ChatGPT or Claude Code, and ask about your email deliverability in plain language. The AI app reads your InboxAlly data through the InboxAlly MCP server: where your mail landed at InboxAlly’s seed mailboxes, how each mailbox provider, sender and domain compares, your sender scores and domain reputation, what changed, and what needs a look. It can also start a placement test for a campaign you’re about to send.
Server address: https://mcp.inboxally.com/mcp
Connect
You sign in with your InboxAlly account, choose a workspace, and approve the connection. The AI app can then use InboxAlly’s tools whenever a question needs them.
Claude
When InboxAlly appears in the directory, open Customize, then Connectors, click +, find InboxAlly and click Connect. Until then, add it as a custom connector:
- In Claude on the web or in Claude Desktop, open Customize, then Connectors.
- Click +, then Add custom connector.
- Name it InboxAlly and enter the server address,
https://mcp.inboxally.com/mcp. - Leave the OAuth client ID and secret empty. If Claude shows an OAuth client choice, keep Use Claude’s published identity: InboxAlly recognizes Claude that way, and doesn’t offer automatic registration.
- Click Add, then Connect if it’s shown. Sign in with your InboxAlly account, choose a workspace, and approve.
On a Team or Enterprise plan, an Owner adds InboxAlly for the organization first, under Organization settings, then Connectors: from Browse connectors when InboxAlly appears in the directory, and until then with Add, Custom, then Web, using the same address and settings. Each member then finds InboxAlly under Customize, then Connectors, and clicks Connect.
Once you’ve connected on the web or in Claude Desktop, InboxAlly also works in the Claude apps for iOS and Android.
ChatGPT
When InboxAlly appears in ChatGPT’s plugin directory, open Plugins in the sidebar, find InboxAlly, install it, and click Connect if asked. Until then, add it as a custom MCP server, in ChatGPT on the web:
- Open Plugins in the sidebar (it’s also in Settings), click Add (+), then Add custom MCP server.
- Name it InboxAlly and add a short description. For the icon, upload InboxAlly’s square logo, so it’s easy to spot.
- For Server URL, enter
https://mcp.inboxally.com/mcp. For Authentication, select OAuth. - Read the warning, tick I understand and want to continue, and click Create as a plugin.
- Click Continue to InboxAlly, sign in with your InboxAlly account, choose a workspace, and approve.
- If InboxAlly isn’t installed yet, open it under Plugins, then Personal, and install it.
Who can add a custom MCP server depends on your ChatGPT plan and workspace. In a Business, Enterprise or Edu workspace, an admin decides whether members can create plugins with MCP servers. On Pro, turn on Developer mode first, in Settings under Advanced settings. Pro may allow only the tools that read, which leaves out starting placement tests.
Claude Code
Run:
claude mcp add --transport http inboxally https://mcp.inboxally.com/mcp
Then type /mcp in Claude Code, select inboxally, and sign in.
Signing in
- Your InboxAlly login. You sign in on InboxAlly’s own sign-in page. The AI app and the MCP server never see your password.
- An approval page. After you sign in, InboxAlly shows which app is connecting and where its access goes, the workspace, your role there, and what the app will be able to do. Nothing connects until you click Connect, and Cancel connects nothing.
- One workspace per connection. You choose the workspace when you connect, and the connection sees only that workspace, with your account’s permissions. InboxAlly checks them on every request, so a change to your access applies at once.
- Starting placement tests. When your AI app asks for it, the approval page also lists Start placement tests (each uses one of your plan’s monthly tests). A connection without that permission can still read everything, but can’t start a test.
- Switching workspace or account. Remove InboxAlly in your AI app’s settings, as under Disconnecting below, then add it again and choose the workspace. The InboxAlly sign-in page remembers you, so to use a different InboxAlly account, sign out of InboxAlly in your browser before adding it again.
What you can ask
- “How did my mail land this week, and how does that compare with last week?”
- “Compare Gmail, Yahoo and Outlook over the last 30 days.”
- “Which of my senders has the lowest primary inbox rate?”
- “What did I send yesterday, and where did it land?”
- “What’s the sender score for news@example.com, and which provider is weakest?”
- “What’s the IA Reputation of example.com?”
- “Which subject lines need a look this week?”
- “What changed for news@example.com since September 1?”
- “Are SPF, DKIM and DMARC passing for example.com at Gmail?”
- “Look inside the latest message my seeds got from news@example.com: which platform sent it, and how did it get there?”
- “Is DMARC set up right for example.com, and does it report to InboxAlly?”
- “Which of my sending domains need attention?”
- “Run a placement test on the newsletter I’m about to send.”
- “Here’s my test segment: does it have exactly the addresses the placement test needs?”
- “Which of my seed mailboxes are inactive? Can I shuffle my seed list now?”
- “Are my HubSpot and Klaviyo integrations healthy?”
- “Plan a warmup for a new domain that will send 20,000 emails a day.”
- “How do I set up a sender profile?” (answered from InboxAlly’s help center)
- “What can this InboxAlly connection do?”
The full list of tools, with what each answers, is in InboxAlly MCP tools.
Placement tests
A placement test shows where one real campaign lands, at InboxAlly’s seed mailboxes, before you send it to everyone. For how placement testing fits alongside content tests and ongoing monitoring, see How does email spam testing work?.
- Start the test when you’re ready to send. The AI app starts it in your InboxAlly account and gives you a test address, the seed addresses, and a deadline to send by. The send window opens when the test starts, so start it only when the campaign is ready.
- Send the campaign yourself. Add every address the test gives you to the campaign’s audience, and send it from your email platform before the deadline. To check them first, put the test’s addresses in a segment of their own, with nothing else in it, and give the AI app that segment’s addresses to compare with the test’s. Neither InboxAlly nor the AI app sends any mail.
- Ask for the results. They fill in as the seed mailboxes receive the campaign, provider by provider.
Each test uses one of the placement tests in your plan for the month, the same allowance the InboxAlly app uses, and a test started here can also appear in the app. If the AI app couldn’t tell whether a test was created, asking it to try again returns that same test rather than starting a second one.
Access
Every tool works with an InboxAlly account, and uses the data and permissions that account already has. Nothing is billed separately for using InboxAlly through an AI app; a placement test uses one of your plan’s monthly tests, as it would in the InboxAlly app.
The connector is not plan-gated: it works with any InboxAlly account, and your role in the workspace decides what it can do. Placement tests draw on the same monthly allowance as the app, so when that allowance is used up, starting one returns a quota error — more come with the next month, or with a plan that includes more tests.
Reading the results
- Seed mailboxes. Placement figures come from InboxAlly’s seed mailboxes: the copies of your mail that reached them and where each one landed. They are not counts of everything you sent through your email platform.
- Primary inbox and inbox including promotions. Primary inbox counts only the main inbox. Inbox including promotions also counts the promotions and social tabs: everything that avoided spam. The two are reported separately and never mixed.
- Percent and points. Rates are percentages from 0 to 100. A change between two rates is in percentage points: a fall from 60% to 50% is 10 points.
- Recent days are still filling in. Seed results keep arriving for up to 72 hours after a send, so the most recent figures can still change.
- Scores are estimates. The IA Score is InboxAlly’s estimate of how likely your next mail is to avoid spam, recomputed daily. Domain reputation, InboxAlly’s IA Reputation, is its own prediction of a sending domain’s reputation, not a mailbox provider’s rating.
- Periods. An answer about a period of time states it, in UTC unless the answer says otherwise.
Every metric is defined in InboxAlly MCP metric definitions, and each answer carries the definitions of the metrics in it.
Your data
- Reading, and placement tests. Most tools read your InboxAlly data or work out a plan. Starting a placement test creates the test in your account, and a help question goes to InboxAlly’s help assistant (below). None changes your settings, sender profiles or lists.
- Help questions. A how-to question goes to InboxAlly’s help assistant, which answers from InboxAlly’s help center, with links to the articles it used.
- No second copy. The MCP server fetches your data from InboxAlly when a question needs it, and doesn’t keep a copy of your reports.
- Your AI app. What you ask, and the answers, pass through the AI app you connected, under that app’s own terms.
How InboxAlly handles your data is in its Privacy Policy.
What it can’t do
- It can’t change your InboxAlly settings. Sender profiles, lists and account settings are read-only through the connector. Starting a placement test is the only thing it creates.
- It never sends your mail. The connector can start a placement test and tell you which addresses to include, but you send the campaign yourself from your own email platform.
- It doesn’t see your whole send. Every placement figure comes from InboxAlly’s seed mailboxes — the copies of your mail that reached them — not from everything you sent through your email platform.
Limits
- Answers sized for AI apps. Long lists come a page at a time, and the AI app asks for the next page when it needs one.
- Rate limits. If requests come too fast, the tool says so, and when to try again. Help questions and DNS record lookups also have daily limits, which reset at 00:00 UTC.
Disconnecting
Remove InboxAlly in your AI app’s settings, and the app stops using InboxAlly:
- Claude: in Customize, then Connectors, click Remove next to InboxAlly, or disconnect it from its three-dot menu. On a Team or Enterprise plan, an Owner removes it for everyone under Organization settings, then Connectors.
- ChatGPT: in Settings, then Plugins, open InboxAlly and click Disconnect, under Connection or in its three-dot menu. Uninstalling the plugin also disconnects it.
- Claude Code: run
claude mcp remove inboxally.
If the app also revokes its access, as the OAuth standard lets it, InboxAlly ends the connection on its side at once. To connect again later, add it as above. Disconnecting the app doesn’t sign you out of InboxAlly in your browser.
Troubleshooting
- Couldn’t reach InboxAlly. Check that the server address is exactly
https://mcp.inboxally.com/mcp, and that your network or firewall doesn’t block it. - Sign-in failed, or authorization failed. Try again. If it fails again, sign out of InboxAlly in your browser, then remove InboxAlly and add it again (in Claude, with Use Claude’s published identity).
- A tool says a permission is missing. Remove InboxAlly from your AI app, add it again, and approve the permission on InboxAlly’s approval page.
- Tools look out of date in ChatGPT. ChatGPT keeps the tool list it read when InboxAlly was added. Open InboxAlly under Plugins and click Refresh, or remove it and add it again.
- Wrong workspace. One connection covers one workspace. Remove InboxAlly from your AI app and add it again, choosing the workspace. For a different account, also sign out of InboxAlly in your browser first.
Frequently Asked Questions
https://mcp.inboxally.com/mcp. You connect it once, signing in with your InboxAlly account and choosing a workspace.Help
For help with InboxAlly, see docs.inboxally.com or email support@inboxally.com.