MCP
Troubleshooting
Connector added but nothing happens, an expired grant, or a client that lists no tools.
Last updated on
Nothing happens when you add the connector
Check the URL has no trailing slash: use https://app.postonus.com/api/mcp, not .../api/mcp/.
The client lists no tools
The connection authenticated, but something failed before tools could register. Two known causes:
- No default workspace. An OAuth connection resolves to your account's default workspace, not a workspace you pick during the flow. If your account has none set, the connection has nothing to bind to. Open the dashboard once and set a default under Settings.
- You are no longer a member of that workspace. Every request re-checks membership, even for a token that hasn't expired. If you were removed from the workspace since connecting, reconnect after joining one you belong to.
The grant expired, or the client asks you to sign in again
OAuth access tokens are short-lived by design, and a client is expected to use its refresh token to get a new one automatically. If it instead asks you to sign in again:
- Disconnecting and reconnecting from AI Assistants in the dashboard clears out any stale grant.
- If you revoked the assistant's access yourself, this is expected — reconnect to grant it again.
Scheduling fails with a quota or payment message
That is not a connection problem. It means your workspace has hit a plan limit or has no active subscription — see Limits. The message names what to do.
A server-to-server integration gets 401
That path uses x-api-key, not OAuth. Confirm the header is set and the key has not been revoked — see API authentication.