valueIQDOCS
Open valueIQ

MCP Server · MCP Server · Troubleshooting

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's config file only accepts local servers. Use Settings → Connectors → Add custom connector with the server URL instead, or bridge the remote server with mcp-remote ("command": "npx", "args": ["-y", "mcp-remote", "https://mcp.valueiq.ai"]). A plain url entry in claude_desktop_config.json is ignored.
  • Cursor uses 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 product, a variant, a deal, a deck export), restoring an archived product, and a DIY Reality Check draw credits from the workspace pool. If the pool cannot cover the action, it does not run and the assistant reports insufficient credits with your balance and the cost. Ask "How many credits do we have left?" to check.
  • If editing or creating a product returns FORBIDDEN, you do not have the value model edit permission in that workspace. Owners and Admins have it; Members need an Owner or Admin to grant it.
  • If the assistant offers no write actions at all, your role is Viewer in every workspace you belong to.
  • Adding someone to a deal team returns NOT_FOUND when that person has no valueIQ account in the workspace yet. Invite them from Settings → Team first.
  • Transient errors are retried automatically. If an error repeats, try again a minute later, and note the exact message if you contact support.

Archiving or restoring a product did not happen

  • The assistant lists first and acts only after you confirm. Archiving shows the product, its variants and each deal that would be archived with it; restoring shows the credit cost and the archived deals. Reply yes (and name the deals to bring back) and it carries on. If a deal was added or removed after the list, it lists again.
  • Archiving, restoring and renaming a product need an Owner or Admin.
  • Restoring draws credits again. If the workspace cannot cover the cost, nothing is restored and the assistant reports the balance and the cost.
  • If fewer deals were archived than the list showed, the rest were not visible to you; ask a deal member or an Admin to archive them.

A story edit was refused

  • Someone else has the story locked for presentation. Only the person who locked it can edit it or release the lock, and the lock expires after four hours.
  • The story is still generating. Wait for it to finish, then try again.
  • You are a Viewer on the deal, or the deal is archived. Restore the deal first.
  • Only a story's owner can bookmark a version. Anyone who can edit the deal can restore a version.

Moving a product through its edit history was refused

  • The product changed outside its history since that edit, for example in a way the history cannot replay. The assistant says which; ask it to show the edit history.
  • Active deals, variants or siblings now depend on a part of the product that the move would change. Archive or move them first, or choose a point that does not cross that change.
  • You need the value model edit permission, and a competitor's model cannot be edited.

Estimate from comparables or the DIY Reality Check is not offered

  • Both are beta features and are only offered to workspaces that have them turned on. If the assistant does not know them, they are not on for you yet.
  • A DIY Reality Check also needs a deal with at least one value driver that has a value, and it cannot run twice at once on the same deal.

A document did not attach

  • Attaching a file takes two steps, start and finish. If the assistant stops after the first, ask it to finish the upload.
  • Accepted types are PDF, images, Word, PowerPoint, text, markdown, RTF, CSV and JSON, up to 50MB. Spreadsheets need the app, because it asks which sheets to use.
  • The deal or product must be linked to its CRM record first. Ask the assistant to link it, giving the CRM record id.
  • valueIQ integrates with leading CRMs. Contact us if your workspace does not yet have a CRM connection.

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.