SendFox
Connect SendFox to manage contacts and lists, send campaigns, build automations, and track email marketing stats.
A SendFox personal access token created under Settings > Connections > API tokens, shown once, pasted into PopMCP's Personal access token field.
Paid plan required before this connector works
SendFox only issues personal access tokens on a paid plan; sendfox.com/pricing lists the Free plan as 'No API access' and the paid Lifetime and Pro plans as 'Full API access'. There is no application and no review.
- Typical wait
- Instant once on a paid plan. There is no review, no application and no developer programme.
- Cost
- Any paid SendFox plan qualifies — the one-time Lifetime deal or a Pro subscription. Check sendfox.com/pricing for the current amounts; the Free plan is listed there as 'No API access'.
- Blocked until approved
- On the Free plan the API tokens page shows an upgrade prompt instead of the token tools, so no token exists and no endpoint (contacts, lists, campaigns) is reachable.
- Works meanwhile
- The API surface is small and fully documented publicly at help.sendfox.com, so requests and payloads can be written against the docs before upgrading.
Where to apply: Upgrade the account, then create the token under Settings > Connections > API tokens (sendfox.com/account/oauth) with the Create New Token button and send it as a Bearer header.
- The token is displayed once only and cannot be recovered; you must create a new one if lost.
- This is a plan gate, not an approval queue. Nobody at SendFox reviews the request, so a support ticket asking for API access gets no faster result than upgrading.
- SendFox's API is intentionally minimal and rate limited; several list and campaign operations that exist in the UI have no endpoint, so check the endpoint list before designing around it.
- The same token also backs the Zapier and WordPress integrations, so revoking it to rotate API credentials silently breaks those connections too.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://api.sendfox.com
Before you begin
- A paid SendFox plan. The API answers HTTP 402 on free accounts.
- Login to the SendFox account that owns the lists, emails and automations PopMCP should manage
Get your credentials
Open the API tokens screen
Click your account dropdown in the top-right corner, then go to Settings, Connections, API tokens. The direct link is sendfox.com/account/oauth.
Connections
Tokens and OAuth clients that can reach your SendFox account.
| Name | Created | Status | |
|---|---|---|---|
| ZapierPersonal access token | Mar 4, 2026 | Active | Delete |
Personal Access Tokens sit above the OAuth Clients section on this page.
Create a personal access token
Under Personal Access Tokens click Create New Token, type PopMCP in the Name field, and click Create.
Connections
SendFox tokens are not scoped. The name is only a label.
Copy the token before closing the dialog
Click Copy and paste the token straight into PopMCP. It is a long Laravel Passport string starting eyJ, so check the whole value came across.
Connections
Shown once. A closed dialog cannot be reopened.
Paste it into PopMCP
Paste the token into PopMCP's Personal access token field and click Connect.
Connect in PopMCP
Open your workspace, choose SendFox in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Personal access tokensecret | In SendFox go to Settings → Connections → API tokens (or open https://sendfox.com/account/oauth) → Create New Token, give it a name, and copy it; SendFox shows it only once. It's sent as the Authorization: Bearer header and stored encrypted; used server-side only. Requires a paid SendFox plan.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against SendFox immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows SendFox as Connected. Asking for your lists or recent emails returns real names instead of a 401 or 402 error.
Troubleshooting
401 Unauthorized
Why: The token was truncated on paste, or it was deleted from the API tokens page. These tokens run to well over a thousand characters, so a partial copy is easy.
Fix: Return to sendfox.com/account/oauth, click Create New Token, and paste the entire string with no whitespace or line breaks.
402 Payment Required
Why: The account is on the SendFox free plan, where the API is unavailable.
Fix: Upgrade to a paid SendFox plan, then reconnect with the same token.
The token was never copied
Why: SendFox displays the value only at creation and cannot show it again.
Fix: Delete that token on the API tokens page and click Create New Token again.
Errors come back as HTML instead of a readable message
Why: The request is missing an Accept header, which SendFox uses to decide the error format.
Fix: Nothing to change in PopMCP, which already sends Accept: application/json. If you are testing by hand in curl, add that header.
Reference
Resend
Connect Resend to send transactional and batch email, and manage domains, broadcasts, contacts, and templates.
Twilio
Connect Twilio to send SMS/MMS/WhatsApp, place and control voice calls, search and buy phone numbers, run Verify (OTP), Lookups, Messaging Services, Conversations, Content templates, and Studio. All of Twilio from one connection.