MCP troubleshooting

Make sure pop-ups are allowed for your assistant, and that you are signed in to the OClever dashboard in the same browser. If it still loops, remove the server from your client, add it again and retry. In Claude Code, run /mcp and choose Authenticate again.

Your account needs access to at least one workspace on a paid plan. Ask an owner or admin in your organization to grant access, or check you signed in with the right account.

The token is wrong, expired or revoked. Check it starts with oc_pat_, that the header reads Authorization: Bearer oc_pat_… with one space, and that it is still listed under Settings → AI assistants. For OAuth connections, reconnect the app.

Check the server is enabled in this chat (Claude: tools menu; ChatGPT: + menu; VS Code: Agent mode tools list). Name OClever in your question. If your client caps tool counts, connect with https://mcp.oclever.com/mcp?tools=discover,reports.

Write tools appear only when the connection has the write or spend scope, the workspace is on Growth or above, and you are not using the /readonly URL. To add a scope, revoke the connection and connect again, ticking the extra permissions.

Your connection can see more than one workspace. Tell the assistant which one (“in the Acme UK workspace”), or reconnect with a single workspace selected.

The tool needs a higher plan: Growth for write and most coin tools, Scale for Prompt Lab and Agent Readiness. The message names the plan. See Plans, coins and limits.

The action costs more than your balance. Ask the assistant to call get_coin_balance to see the balance and reset date, or reduce the job (fewer engines or prompts).

You hit 120 calls or 10 coin actions in a minute on this connection. Wait for the time in the message. Assistants that loop through many prompts should use list tools with a higher limit instead of one call per item.

Write tools preview by default. The change only happens when the tool is called again with preview: false. Ask the assistant to apply the preview.

The period may be before your first run, or a filter (engine, region, topic) may exclude everything. Ask for list_engines and list_regions to check names, and try the default 28-day period.

Allow outbound HTTPS to mcp.oclever.com and dashboard.oclever.com, and make sure your proxy does not buffer streaming responses.

This lists the tools your token can use. A 401 means the token is not valid; a JSON list of tools means the server and token are fine and the problem is in the client's configuration.

curl -s https://mcp.oclever.com/mcp \
  -H "Authorization: Bearer $OCLEVER_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Email [email protected] with your client and version, the time of the failed call, and the error text. Never send the token itself; the first characters shown in the dashboard (for example oc_pat_ab12) are enough for us to find it.