Skip to content
Mailgi logo

Mailgi MCP server

Which MCP servers are Mailgi's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-01

← Back to Mailgi

Whose server it is
  • Registry namexyz.mailgi/mailgiverified in the MCP registry

The registry name sits under mailgi.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-01
  • Stateanswerschecked 2026-11-01
  • Tools67
  • Server calls itselfmailgi
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-11-01 the server answered initialize and tools/list without a sign-in. First answer in 229 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • Keep approval on for mail_send, mail_delete: they delete, send or pay without saying so.
  • agent_delete, mail_send, mail_delete, mail_set_flags, mailbox_create change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 33 of 67 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-11-01
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer253 ms
  • Space in an agent's context≈ 6,039 tokensthe definitions of all its tools (67), which an agent carries on every turn
  • Tool definitionsA · 92 of 100
  • Typed results0 of 67 toolsdeclared outputSchema: results come typed, read once
  • No description an agent can choose by: 1 of 67
  • Parameters without a description: in 33 of 67

What an agent can do with it

  • not sure · triage support messages and reply in context
  • not sure · negotiate meeting times over email threads
  • not sure · receive signup verification codes automatically

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that delete, send or pay, marked as not destructive: mail_send, mail_delete
  • Tools that change data, on a server that answers without a sign-in: agent_delete, mail_send, mail_delete, mail_set_flags, mailbox_create

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers67 tools · read 2026-11-01
  • register_agent

    Creates a new agent with its own email address and returns its API key, shown once.

  • org_login_request_code

    Emails a 6-digit dashboard login code to a human's address. Creates the account on first login.

  • org_login_verify

    Exchanges an emailed login code for a dashboard session token.

  • topup_lookup

    Shows which wallet a top-up for a Mailgi address would credit, and the allowed amounts.

  • topup_start

    Creates a card payment link for the wallet behind any Mailgi address. Give it to a human to pay.

  • topup_status

    Returns whether a top-up payment has been paid and credited.

  • health

    Checks that the Mailgi API, its database and the mail server are up.

  • agent_get

    Returns this agent's profile: its addresses, label and domain.

  • agent_usage

    Returns this agent's daily send and API counters; the latest day is partial.

  • agent_delete

    Permanently deletes this agent, its mailbox and all its API keys.

  • mail_list

    Lists message headers in the mailbox, newest first by default; filter by folder with mailboxId.

  • mail_get

    Returns one message with its full text and HTML body.

  • mail_send

    Sends an email from this agent's address. Mail to outside addresses is charged to the wallet.

  • mail_delete

    Moves a message to the Trash folder.

  • mail_move

    Moves a message to another folder.

  • mail_set_flags

    Marks a message as seen or unseen, flagged or unflagged.

  • mailbox_list

    Lists all folders, including Inbox, Sent and Trash.

  • mailbox_create

    Creates a folder, optionally nested under another.

  • mailbox_rename

    Renames a folder.

  • mailbox_delete

    Deletes a custom folder.

  • apikey_list

    Lists this agent's API keys. Key values are never shown again.

  • apikey_create

    Creates another API key for this agent. The key is shown once.

  • apikey_revoke

    Revokes an API key immediately.

  • billing_get

    Returns the wallet this agent spends from: balance, prices and how to top up.

  • billing_topup

    Creates a card payment link for this agent's wallet. Give it to a human to pay.

  • billing_transactions

    Lists the wallet ledger, newest first.

  • webhook_list

    Lists this agent's webhook endpoints.

  • webhook_create

    Registers an HTTPS URL to be notified when mail arrives. The signing secret is shown once.

  • webhook_delete

    Deletes a webhook endpoint.

  • webhook_deliveries

    Lists recent delivery attempts for a webhook endpoint.

  • webhook_resend

    Queues a delivery attempt to be sent again.

  • webhook_enable

    Re-enables a webhook endpoint that was switched off after repeated failures.

  • org_me

    Returns the signed-in user and the organizations they belong to.

  • org_logout

    Revokes the current dashboard session token.

  • org_list

    Lists the organizations the signed-in user belongs to.

  • org_create

    Creates an organization; the signed-in user becomes its owner.

  • org_get

    Returns one organization.

  • org_rename

    Renames an organization.

  • org_member_list

    Lists an organization's members and their roles.

  • org_member_set_role

    Changes a member's role.

  • org_member_remove

    Removes a member from the organization, or leaves it when userId is your own.

  • org_invite_create

    Emails an invitation to join the organization.

  • org_invite_list

    Lists pending invitations.

  • org_invite_revoke

    Revokes a pending invitation.

  • invite_accept

    Accepts an organization invitation with the token from the invite email.

  • domain_attach

    Attaches a custom domain and returns the DNS records to publish.

  • domain_list

    Lists an organization's custom domains.

  • domain_get

    Returns a domain's verification status and the DNS records it needs.

  • domain_verify

    Re-checks the domain's DNS records and verifies it if they are correct.

  • domain_detach

    Detaches a custom domain from the organization.

  • domain_inbox_list

    Lists the inboxes (agents) on a domain.

  • domain_inbox_create

    Creates an inbox with a chosen address on a domain. Its API key is shown once.

  • domain_inbox_delete

    Removes an inbox and its mail from a domain.

  • regtoken_create

    Creates a token that lets an agent register its own address on this domain. Shown once.

  • regtoken_list

    Lists a domain's registration tokens.

  • regtoken_revoke

    Revokes a registration token.

  • org_usage

    Returns daily send, receive and API counters across the organization.

  • domain_usage

    Returns daily send, receive and API counters for one domain.

  • org_billing_get

    Returns the organization's shared wallet: balance, prices and how to top up.

  • org_billing_topup

    Creates a card payment link for the organization wallet.

The first 60 of 67, as the server listed them.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "mailgi": {
      "type": "http",
      "url": "https://api.mailgi.xyz/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http mailgi https://api.mailgi.xyz/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.mailgi.xyz/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.