Troubleshooting

Most MCP problems come down to one of five things. Work through the heading that matches what you are seeing.

Tools aren't appearing after setup

Check the server URL is exactly https://mcp.valueiq.ai.
If you edited a config file (Claude Desktop, Cursor, VS Code), save it and fully quit and relaunch the client. Claude Desktop does not pick up the server until you restart.
On claude.ai, valueIQ tools appear in new chats after you approve the connection, not in chats already open.
In ChatGPT, enable the connector from the tools menu inside the chat. Custom connectors also need a paid plan that supports developer connectors.
In VS Code, tools are only available in Copilot Chat in Agent mode.

Authentication is failing

Sign-in happens in a browser tab the first time you use a valueIQ tool. Complete the OAuth consent screen there, then return to the client.
There is no API key, token, client ID or secret. If your client shows fields for them, leave them empty.
On claude.ai Team and Enterprise plans, an organisation Owner adds the connector first under Organization Settings → Connectors. Each member then clicks Connect to sign in.
If you revoked the client earlier from Workspace Settings → Developer, run the setup steps again and approve the connection when prompted.

Config syntax looks wrong or outdated

Vendor configuration syntax changes. The valueIQ side is always the same: the server URL and OAuth on first use. The vendor's docs are the canonical source for the rest, and each client page links to them. Two things to check first:

Claude Desktop and Cursor use an mcpServers block with a url field.
VS Code uses a servers block with "type": "http" and a url field.

Tools appear but return errors

Confirm the active workspace. The workspace switcher in the top-left header of the app controls every list the assistant can see. A deal in another workspace returns nothing.
The deal or product may still be generating. A deal shows "Researching…" while its customer variables are built, and a product shows "Surveying Market" until its market values are computed. Wait for the completion toast, then try again.
Actions that create something (a deal, a deck export) draw credits from the workspace pool. If the pool cannot cover the action, it does not run.
Transient errors are retried automatically. If an error repeats, try again a minute later, and note the exact message if you contact support.

I connected successfully but the assistant doesn't know my deals

Name the deal by company name or deal name. That is what search matches.
Ask it to list the deals in the workspace first. If the list is empty or wrong, you are in the wrong workspace.
Archived deals are hidden by default, and closed deals are filtered out of the default pipeline view.
The assistant only sees what your role lets you see. If the deal is in a workspace you are not a member of, ask an Owner or Admin to add you.