Skip to main content

​
Connector Is Missing or Unavailable

ChatGPT and Claude workspace administrators can control which connectors members may use. If Coval is visible but cannot be installed or enabled, ask a workspace administrator to allow it.
Install Coval from the ChatGPT plugin listing or Claude connector directory. For Codex or another MCP client, use:
After installing or connecting, start a new conversation and enable Coval if the client offers a connector or tools picker. Some clients discover tools only when a new conversation starts.

​
Hosted Connector Does Not Connect

The hosted connector URL is exactly:
Remove an older API-key or mcp-remote configuration before adding the OAuth connector.
Disconnect Coval in your client’s connector settings, add it again, and complete the browser flow. Select a Coval organization before approving access.
If codex mcp login coval reports invalid_scope for user:org:read, update Codex and retry:
Some clients discover tools only when a new conversation or task starts. After authorization succeeds, open a new one and ask it to list your Coval agents.

​
Wrong Organization or Permission Error

The hosted connector is bound to the organization selected during OAuth consent. Disconnect and reconnect Coval, then choose the intended organization. Your Coval user must already be a member of that organization. An identifier from another organization returns a not-found or permission error. The connector does not use the identifier to switch organizations.

​
Tools Are Missing

The hosted connector should expose 19 tools, including consult_sofia.
  1. Disconnect and reconnect the hosted connector.
  2. Start a new task so the client refreshes tool discovery.
  3. Confirm the configured URL ends in /mcp.
  4. If only consult_sofia fails, verify that direct read tools work and send the error and timestamp to Coval Support.

​
Local Server Problems

The local npm server requires Node.js 20 or later and a valid Coval API key.
If the package starts but API calls fail, create a fresh key in Coval Settings and check for leading spaces or line breaks. For corporate networks, allow outbound HTTPS to:
  • mcp.coval.dev for the hosted connector
  • api.coval.dev and registry.npmjs.org for the local npm server

​
Still Stuck?

Include the following when contacting support@coval.dev:
  • MCP client and version
  • Operating system
  • Approximate failure time and timezone
  • The exact error text, with access tokens and API keys removed
  • Whether direct tools, consult_sofia, or both failed
You can also open an issue in the public Coval MCP repository. Do not include credentials or customer data in a public issue.