Troubleshooting connections and answers

Most issues fall into four cases. Run the fix for each before you write in.

Tools not appearing

Reload the window first. For Claude Desktop, fully quit with Cmd-Q and reopen. A window close isn't enough. If the Granova tools still don't show, re-run the connect flow from /connect. Your credits and history stay attached to your email.

401 Unauthorized

Your token expired or was revoked. Re-run the connect flow to refresh it. If a refresh keeps failing, sign out and back in at /login, then reconnect. Email support@granova.ai from the address on your account if it persists.

Agent connected but won't call tools

Some host models don't call MCP tools on the first turn unless asked. Name the tool explicitly: use the Granova ask_expert tool to find what Anthony says about paid search budgets. If the answer still feels generic, the host model may be skipping the tool call. Try a different client (Claude tends to call tools most reliably).

Windows header mangling

On Windows, some shells mangle the Authorization:${}AUTH_HEADER env-var pattern Claude Desktop uses. Use a plain Authorization: Bearer YOUR_API_KEY line in the env block if the bridge won't start.

insufficient_context is correct behavior

When an answer comes back insufficient_context, the expert hasn't covered that topic. It's not a bug. Your credits aren't spent. The gap is flagged for the expert to fill. You can also use submit_question to add the topic to their review queue (no credits, no SLA).

Still stuck?

Email support@granova.ai or use the form on /support/contact. Tell us the client, the symptom, and the exact error text.