Troubleshooting

No tools showing, 401s, tools that vanish, calls that fail — the causes and the fixes.

Work down this list in order. The first two checks catch almost everything.

1. Is the server answering you?

Take the client out of the picture first:

curl -X POST https://www.amnt.io/api/mcp \
  -H "Authorization: Bearer $AMNT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A list of tools — the server and your key are fine. The problem is the client config; jump to step 3.
{"tools":[]} — connected, but this key exposes nothing. Step 2.
401 — the key is wrong, revoked, or has a stray newline. Create a fresh one.

2. Connected, but no tools

The tool list is empty for exactly three reasons:

The key is set to REST only. Change it in Settings → API Keys.
It is on My agents and you have not published a live agent yet. Either publish one or switch the key to Chosen agents and tick some.
An agent you expected is not live — a draft or unpublished agent never appears.

3. The client cannot see the server

Restart properly. Claude Desktop needs a full quit, not a window close. Cursor needs the MCP panel toggled off and on.
Check the JSON is valid. One trailing comma and the whole config file is skipped, usually silently.
```
cat ~/.cursor/mcp.json | python3 -m json.tool
```
Confirm the header key. It is headers with an Authorization entry — not env, not apiKey.
If the client only speaks stdio, use the mcp-remote bridge shown in Connect your client.

4. Tools appear but calls fail

Message	Cause and fix
"Not enough credits"	Top up. The message says what the run costs and what you have
"Agent not found"	The agent was unpublished or renamed since your client last listed tools. Restart the client to refresh
A validation message	The assistant sent a value the agent rejects. The message names the field; it usually fixes itself on the next attempt
"Rate limit exceeded"	60 requests a minute per key, and listing counts. Wait a minute

Most clients ask for the tool list only when they connect. After changing a key's scope, or publishing a new agent, restart the client. Nothing is cached on our side — the list is built fresh on every tools/list.

Still stuck

Send us the curl output from step 1, with the key redacted, via Contact. It tells us in one look whether the problem is the key, the scope or the client.

1. Is the server answering you?

2. Connected, but no tools

3. The client cannot see the server

4. Tools appear but calls fail

5. Tools are stale

On this page