Skip to main content
Every client uses your region’s server URL. Use the one that matches where you sign in to Cotool, or copy it from Settings → MCP: The commands and config on this page have a tab for each region. A connection made with the wrong region’s URL signs in to the wrong Cotool and won’t find your account. You add the URL once in the app’s settings. When the app first connects, a browser window opens to Cotool. Sign in with your normal Cotool login, check which account and organization the app will act as, and select Connect. There is no API key to create or paste.
Every app can connect unless an admin has turned the MCP server off. If the consent screen says MCP is off, ask an admin. See Turn the MCP server off.

​
Claude

  1. In the Claude app or on claude.ai, open Customize → Connectors, select Add, then Custom → Web.
  2. Name it Cotool and paste your region’s server URL.
  3. Select Continue through setup, then sign in to Cotool.
One connector covers Chat, Cowork, and Code, in the app and on the web.

​
ChatGPT

  1. In the ChatGPT app, open the Customize tab in the left rail and select Plugins.
  2. Select Add at the top right, then Add custom MCP server.
  3. Name it Cotool, paste your region’s server URL, and sign in to Cotool.
On chatgpt.com, open Plugins, select +, then Add custom MCP server.

​
Cursor

Add the server to ~/.cursor/mcp.json:
Then open Cursor Settings → MCPs. Cotool shows under Needs Attention; select Authenticate and sign in to Cotool.
Use the global ~/.cursor/mcp.json rather than a project’s .cursor/mcp.json, so the connection follows you across projects and isn’t committed to a repository.

​
VS Code

Add the server:
Then start cotool from the MCP: List Servers command and sign in to Cotool.

​
Other MCP clients and custom agents

Add your region’s server URL (https://app.cotool.ai/api/mcp or https://eu.cotool.ai/api/mcp) as a remote MCP server using the Streamable HTTP transport with OAuth. The client must support:
  • OAuth 2.1 with PKCE
  • Dynamic client registration, or a client ID metadata document
  • Discovery from the server URL, through the /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server metadata
Most current MCP SDKs handle all of this when you give them the server URL. Access tokens last one hour and refresh automatically; a refresh token that has already been used disconnects the app, and you sign in again.

​
Troubleshooting

  • Sign-in doesn’t recognize your account. Check the app uses your region’s URL: eu.cotool.ai if you sign in to Cotool at eu.cotool.ai, app.cotool.ai otherwise. Remove the server from the app and add it again with the right URL.
  • The consent screen says MCP is turned off. An admin needs to turn on Allow apps to connect in Settings → MCP.
  • The consent screen asks you to switch back to your own organization. You’re viewing another organization in Cotool. Switch back to your own, then connect again.
  • The app stopped working. It may have been disconnected in Settings → MCP, or the MCP server was turned off. Reconnect it from the app’s MCP settings.
  • A tool is missing. Tools for features that are off for your organization, such as Detections or Log Ingest, aren’t listed.