Troubleshooting
It will not connect
Check the URL has no trailing slash.
https://automette.com/api/mcpWith an API key, check the header is exactly:
Authorization: Bearer dg_your_key_hereA key that has been deleted, or one from a different account, produces the same "could not connect" as a typo.
With a sign-in, the browser step has to complete. If you closed the tab or it timed out, remove the connector and add it again.
It connected, but there are no tools
Usually a client that has not refreshed. Disconnect and reconnect. In Claude
Code, /mcp shows the tool count next to the server.
It made something and I cannot find it
Check which team is active in the dashboard. A connection acts on exactly one team — the one the key belongs to, or the one that was active when you approved the sign-in. If you belong to several, work can land in a team you are not currently looking at.
To move it, switch team in the dashboard and connect again, or use a key created in the team you want.
It says something does not exist
The assistant sees only what that team can see. A template in another team is genuinely invisible to it — not hidden, absent.
A render cost a credit and I only wanted to look
Previewing is free; rendering is not. If you asked for a document, you got a document.
Say "preview" or "show me what it would look like" when you are still
iterating. preview_template is the free one, and an assistant will use it if
your wording makes clear you are not finished.
Every render appears in History with its source, so you can always see what was spent and by which route.
I want to cut it off
A sign-in: Settings → Connections → revoke. Personal to you.
An API key: API Keys → delete. This also stops any REST integration using the same key.
Revoking takes effect on the next request. Nothing is queued and nothing completes afterwards.
It is slow
The first render after a quiet period is slower — the render service starts cold. Subsequent ones are quick. Nothing is wrong, and nothing is lost if the assistant waits.
Last updated on