Help Desk
Notes from the post office.
Most questions about mailconnect fall into one of a few buckets — installing the recipe, disconnecting, and the occasional “why isn’t Poke seeing my mailbox?” The notes below should cover the common ones. If they don’t, write to us directly; a real person will read it.
Common questions
How do I install the mailconnect recipe?
When the recipe is published, you’ll install it from inside Poke just like any other recipe. Tap install, work through the consent screen, sign in to Fastmail when it asks, and the connection is live. There’s nothing to copy and paste, no MCP URL to enter by hand, and no Fastmail app to set up on your side.
You don’t need to register your own Fastmail app — mailconnect uses a single shared Fastmail OAuth client, and your install just authorizes against it.
How do I disconnect, and what gets deleted?
Two options, both work:
- Remove the recipe from inside Poke. The MCP grant is revoked, and the encrypted Fastmail tokens stored against it become inaccessible.
- Revoke the mailconnect app inside your Fastmail security settings. The upstream tokens stop working immediately, even before Poke notices.
Either action breaks the bridge. There’s no separate “account” on mailconnect’s side to delete — your only data here is the OAuth grant itself.
Poke says it can’t see my mailbox. What now?
Usually one of two things:
- Stale grant: remove and reinstall the recipe inside Poke. The fresh consent flow re-mints both sets of tokens.
- Revoked upstream: if you revoked mailconnect in Fastmail, the bridge can’t recover on its own. Reinstall the recipe from Poke.
Can mailconnect send, archive, or delete email?
No. The current build is strictly read-only. The exposed MCP tools cover get_account_profile and list_mailboxes only — no message bodies, no headers, no sending, no moving, no deleting. Write actions, when they ship, will live behind their own scopes and a separate consent — they will never be enabled by surprise.
Does mailconnect work with multiple Fastmail accounts?
Each recipe install is one Fastmail account. If you have more than one Fastmail account, you can install the recipe more than once. Today, installing the recipe a second time for the same Fastmail user inside the same Poke account will replace the previous grant for that pair.
I’m a developer — can I point a custom MCP client at this?
Yes. The bridge is a plain MCP authorization server, so any MCP-aware client can connect to it directly. The production endpoint is https://api.mailconnect.app/mcp, with OAuth metadata at /.well-known/oauth-authorization-server. This path is for development and debugging — for the normal Poke onboarding, install the recipe instead.
The Worker source is small and single-purpose. If you’re evaluating mailconnect for a sensitive context and want to read it first, write to us and we’ll point you at the repository.
Status
mailconnect is hosted on Cloudflare Workers. There is no separately published status page yet — if Poke is reaching the bridge but the bridge can’t reach Fastmail, you’ll typically see a clear OAuth or JMAP error in Poke’s tool output. If something looks broken in a way that doesn’t, please report it.
Reach a human
Email is the right channel — fitting, given the product. We aim to reply within two business days, sooner if it’s a clear breakage.
Write to support
For connection issues, security questions, or anything that doesn’t fit the FAQ above.
support@mailconnect.appIf you’re reporting a security concern, please put SECURITY in the subject line so it gets routed correctly. We’ll acknowledge receipt within one business day.