SendFox MCP server for your AI

No. SendFox's API requires a paid plan — Lifetime or Empire — so a free account can't connect. Once you're connected, get_current_user is the fastest sanity check: it returns the authenticated user plus the current contacts_count and the plan's contact_limit.

One field: a Personal access token, which you copy out of SendFox and paste once. There are no OAuth popups and no refresh cycle to keep alive. The token is scoped to a single SendFox account, so the connection can only ever see that account's contacts, lists, campaigns and automations.

Lists — create, rename, soft-delete, and add or remove a contact's membership — plus automations and the individual email steps inside them, custom contact fields, subscription forms, and sender domains. get_automation returns an automation's triggers, its email items and per-campaign stats in one call. create_domain adds a sender domain by creating the SendGrid whitelabel domain behind it.

No. create_contact upserts by email, so an address already in the account is updated rather than duplicated, and batch_import_contacts applies the same rule to as many as 1,000 contacts in a single request. add_contact_to_list is idempotent too, though it only works on a contact that already exists — create the person first. On reads, contacts and campaigns come back 100 per page and custom contact fields 20 per page, so a large account takes several calls to walk.

Only if you allow it. send_campaign delivers a draft immediately, which is why most teams keep approval required for writes, or run the connection read-only when they only want reporting. Also worth knowing: update_campaign edits drafts only, so once a campaign has gone out its content is fixed and the agent can only read it back with get_campaign and get_campaign_stats.

delete_contact is a soft delete, and it also cancels any deliverables already scheduled for that person; delete_list and delete_automation are soft deletes as well, and removing an automation cancels everything it had queued. delete_campaign applies to drafts only. unsubscribe_contact is global — that person stops receiving all future email from the account, not just one list — so if you only want someone off a single list, remove_contact_from_list drops the membership and leaves the contact in place. The exception is delete_contact_field, which removes a custom field permanently.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 48 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 33-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 48 here. A trigger is something PopMCP watches for you: 9 SendFox events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into SendFox.