> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cotool.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Use Cotool from ChatGPT, Claude, Cursor, Codex, VS Code, or your own agents

Cotool runs a remote [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server. Connect it to an AI app and that app can work with your agents, alerts, detections, logs, and integrations, acting as you and with your permissions.

There are no API keys. You add one URL to your app, sign in with your normal Cotool login, and approve the connection.

## Server URL

The server URL depends on your region. Copy it from **Settings → MCP** in Cotool, or use the one that matches where you sign in:

| Region | You sign in at | Server URL |
| - | - | - |
| US | [app.cotool.ai](https://app.cotool.ai) | `https://app.cotool.ai/api/mcp` |
| EU | [eu.cotool.ai](https://eu.cotool.ai) | `https://eu.cotool.ai/api/mcp` |

Add it to your app's MCP or connector settings, not to a chat message. See [Connect an app](https://docs.cotool.ai/mcp/connect-clients.md) for the steps in each client.

## Turn the MCP server off

The MCP server is on for every organization. Admins can turn it off in [Settings → MCP](https://app.cotool.ai/settings/mcp) ([eu.cotool.ai/settings/mcp](https://eu.cotool.ai/settings/mcp) for EU organizations) with **Allow apps to connect**. Turning it off takes effect immediately, including for apps that are already connected.

Admins can also disconnect any connected app from the same page.

## What a connected app can do

An app acts as the person who connected it. It can do what that person can do in the Cotool web app and nothing more: the same role, permissions, and organization.

| Area | What the app can do |
| - | - |
| Search | Search the Cotool docs and your agents, alerts, detections, and integrations |
| Agents | List, read, create, update, and run agents, and read agent runs |
| Alerts | Search and read alerts and their timelines, change status and severity, add comments |
| Detections | List and read detections, change schedules, and start tuning runs |
| Logs | List log tables and run log queries |
| Integrations | List integrations, read setup guides, and save non-secret connection settings |

Tools for features that are off for your organization, such as Detections or Log Ingest, aren't available.

Apps can add library detections, which publishes the library's code and enables its schedule. They can't directly publish edits to detection code, approve or reject tuning proposals, or delete anything.

## Secrets stay out of chat

An app never sends or stores integration secrets such as API keys, client secrets, or passwords.

* When an integration needs a secret, the app gives you a link instead. The link opens the integration's connect form in Cotool, prefilled with the non-secret values, and you enter the secret there.
* If an app sends a secret anyway, Cotool rejects it without storing it. Rotate that secret, because it has passed through the app's chat history.

## Manage connections

The **Connections** table in **Settings → MCP** lists every connected app, who connected it, and when it was last used. Admins see the whole organization; everyone else sees their own connections.

Select **Disconnect** to revoke an app's access immediately. Connecting it again requires signing in.

## Audit log

Every tool call is recorded in the [audit log](https://docs.cotool.ai/settings/audit-logs.md) as `user.calledMcpTool`. Changes an app makes, such as updating an alert, show as made by the user through that app, and the Audit Logs page can filter by app type. Connecting and disconnecting apps and changing MCP settings are recorded too. See the [MCP events](https://docs.cotool.ai/settings/audit-log-events.md) in the event reference.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.