Connecting clients
Troubleshooting
The three things people hit most — and how to fix them. When in doubt, validate with curl to separate a connection problem from an entitlement one.
Tools aren’t showing up
- Refresh / reconnect the connector. Entitlement changes emit
tools/list_changed, but in the current stateless transport that signal is recorded server-side, not pushed live — so reconnect (see below). - Check your packs and plan. The tool list is the intersection of your plan and enabled packs. Only seeing core tools means the rest aren’t enabled for your membership. Run
_status, then check Packs and Plans. - Check member restrictions. An owner/admin may have restricted your membership to a subset of packs. An org admin can adjust this in the dashboard.
- Check per-user tool curation. If you turned tools off for yourself in the dashboard, re-enable them.
Authentication failures
- Wrong or expired key. Keys can expire; an expired or revoked key is rejected with a
401. Create a fresh one at API keys (shown only once). - Missing
Bearerprefix. The header must readAuthorization: Bearer pp_mcp_…with the literal wordBearerand a single space. - Pasted the wrong thing. An invite token or OAuth secret is not an MCP key — MCP keys start with
pp_mcp_. - Plan inactive. If the subscription lapsed and reset to free, paid-pack tools disappear and may return access-denied even when the key authenticates. Check billing.
- OAuth stuck in a loop. Usually the host attached the token to the bare host — re-add the connector with the explicit
https://mcp.pocketpart.io/mcpURL.
list_changed isn’t refreshing
Your plan or packs changed but the client still shows the old tools. Because the transport is stateless, clients must reconnect to pick up the new set:
- Claude.ai: Settings → Connectors → PocketPart → Disconnect, then reconnect (re-authorize, same org).
- Claude Code / Desktop: restart the app, or
claude mcp remove pocketpartthen re-add. - Cursor: Settings → MCP → toggle the server off then on, or restart Cursor.
- ChatGPT: remove and re-add the connector, or start a new chat.
After reconnecting, run _status to confirm the new packs are reflected.