Read audiences, groups, mailings and campaign results without sending email or changing contacts. For marketing teams reporting on Emma audiences and email campaigns. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"emma": {
"url": "https://emma.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"emma": {
"type": "http",
"url": "https://emma.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
See audience groups and their member counts, then inspect the members in a group. Follow additional pages when you need the complete group membership.
emma_list_groups emma_list_group_members
Find recent mailings and review their delivered messages, opens, clicks and opt-outs alongside account-level response statistics.
emma_list_mailings emma_get_mailing_response emma_get_response_summary
Review which links received clicks in a mailing and inspect recipient activity to understand how people interacted with the campaign.
emma_list_mailing_links emma_list_mailing_activity
The login page asks for your Emma account id, Public API key and Private API key.
In Emma open Account settings → API Key and click Generate API Key: that page shows the account id, public key and private key (agency accounts: Menu → Accounts → the account's settings → API key, and use that sub-account's own id). See the Emma API documentation. Your keys are used only to call the Emma API on your behalf; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Emma account id, Public API key and Private API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Emma connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
emma_list_groups | read | List groups List the member groups (audience lists) of the Emma account with their active, opted-out and error member counts. Defaults to normal groups; group_types can add test and hidden groups. |
emma_get_group | read | Get a group Get one member group with its member counts (active, opted-out, error). |
emma_list_group_members | read | List group members List the members of one group (email, status, custom fields). Paged: use next_start for more. |
emma_list_members | read | List members List the members (contacts) of the whole audience: id, email, status (a active, o opted out, e error), custom fields, bounce count. Paged: use next_start for more. With count_only the reply is just the number of members. |
emma_get_member | read | Get a member Get one member by id, with all custom fields, status, SMS status and bounce count. |
emma_find_member_by_email | read | Find a member by email Find one member by email address, with all custom fields and status. A 404 means the address is not in the audience. |
emma_get_member_groups | read | Get a member's groups List the groups one member belongs to. |
emma_get_member_mailings | read | Get a member's mailing history The mailing history of one member: which mailings they were sent and what they did with them. |
emma_list_fields | read | List member fields List the custom member fields of the account (shortcut names, display names, types). |
emma_get_import | read | Get an import Status and results of one bulk member import (by import id), or, without an id, the list of all imports of the account. |
emma_list_mailings | read | List mailings List mailings (campaigns): id, name, subject, sender, status (p pending, a paused, i injecting, s sending, x canceled, c complete, w waiting, u unapproved, f failed), type, recipient count, scheduled time. Defaults to standard and test mailings in all statuses, newest first. Paged: use next_start. |
emma_get_mailing | read | Get a mailing Get one mailing in full: content (HTML and plain text), recipients (groups, searches, segments), links, schedule, status. |
emma_list_mailing_members | read | List a mailing's members List the individual members a mailing was sent to (not groups or searches). Paged: use next_start. |
emma_get_response_summary | read | Account response summary Month-by-month response statistics for the whole account: mailings, sent, delivered, bounced, opened, clicked, forwarded, opt-outs, sign-ups (test mailings excluded). |
emma_get_mailing_response | read | Get a mailing's response Response summary of one mailing: recipients, sent, delivered, bounced, opened, clicked (unique and total), forwarded, opt-outs, sign-ups. |
emma_list_mailing_links | read | List a mailing's link clicks The links of one mailing with their unique and total clicks. |
emma_list_mailing_activity | read | List mailing activity Who did what with one mailing: members it was sent to (sends), still in the queue (in_progress), delivered or bounced (deliveries), opened (opens), clicked (clicks), forwarded, opted out (optouts) or signed up (signups). Each row has the member's email and timestamp. Paged: use next_start. |
emma_list_searches | read | List saved searches List the saved searches (dynamic segments) of the account, with their criteria. |
emma_get_search_members | read | List a search's members The members that currently match a saved search. Paged: use next_start. |
emma_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
emma_request_feature | Request a missing feature Tell usefulapi that the user needs something the Emma tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
emma_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Emma (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
emma_cancel_subscription | Cancel the Pro subscription Cancel the caller's Emma Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run emma_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper connected account | $9/mo · $90/yr | 10,000 tool calls / month |
Pro covers this Emma server only. Subscribe with emma_upgrade (it returns a Stripe Checkout link). Cancel any time with emma_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running emma_upgrade before then undoes the cancel. Or write to [email protected].
Review audience groups and membership. Compare email campaign results. Inspect link clicks and recipient activity. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Emma. The server calls the Emma API with your own Emma access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Emma account id, Public API key and Private API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Emma account id, Public API key and Private API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Emma API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Emma.
All 19 Emma tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month tool calls, for this Emma server only. Cancel any time: Pro then runs to the end of the paid period. Run emma_usage_status to see how many calls you used.
Ask the AI to run emma_upgrade: it returns a Stripe Checkout link. To cancel, run emma_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with emma_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.