MCP servers
The MCP servers integration lets you connect any remote Model Context Protocol (MCP) server — Linear, GitHub, Notion, Atlassian, or a server your own team runs — so the AI assistant can use its tools in the same conversation as your cost, anomaly, insight, and CloudFlow data.
An administrator connects a server once for the organization and decides which of its tools the assistant may use. Each user then authorizes their own account with the third-party service; the assistant acts as that user, with that user's permissions, and every action is attributed to them.
Required permissions
-
DoiT account: Adding, changing, or removing MCP servers requires Manage settings. Any user with access to the AI assistant can authorize or revoke their own account.
-
Third-party service: You need an account in the connected service with permission to grant an application access on your behalf. Some services, such as GitHub, also require an administrator to register an OAuth app first.
Connect a server
-
Sign in to the DoiT console, select Data ingestion and integrations > Integrations from the top navigation mega menu.
-
On the MCP servers card, select Manage, then Add server.
-
Choose a service (Linear, GitHub, Notion, Atlassian) or Custom server, and enter a name and the server's URL. Custom servers must use
httpsand the Streamable HTTP transport. -
Read and accept the acknowledgement, then select Connect. The platform checks the URL, contacts the server, and detects how it authenticates:
- A public server is ready immediately and its tools appear in the server details.
- A server that uses OAuth asks you to authorize your own account before its tools can be discovered. Select Authorize to discover tools and complete the sign-in in the window that opens.
- A service that does not register applications automatically (for example GitHub) asks for the Client ID and Client secret of an OAuth app you registered with that service. Use the callback URL shown in the dialog when you register the app.
Servers that require a static API key or another credential the platform cannot obtain on your behalf are not supported yet.
Choose which tools the assistant may use
Open a server's Details to review its tools. They are grouped by what the server declares about them:
| Group | Default | Behavior |
|---|---|---|
| Read-only | Enabled | Runs without asking. |
| Write | Enabled, asks before running | The assistant shows the exact request and waits for you to select Run or Cancel. |
| Destructive | Disabled | Stays off until an administrator enables it. |
Toggle Enabled and Ask before running per tool, then select Save changes. Tools that appear after a refresh are marked New and keep the default for their group until you review them; the server is flagged Tools changed.
Use Refresh tools from the row menu to re-read the server's tool list, Disable to pause a server without losing its configuration, and Remove to delete it together with every user's authorization.
Authorize your account
For OAuth servers, every user authorizes separately:
- From Integrations > MCP servers, select Authorize on the server row and complete the sign-in in the window that opens.
- In a conversation, when the assistant needs a server you have not authorized yet, it shows an Authorize card. Authorize in the window that opens, then select Retry so the assistant continues.
Your access shows whether your authorization is active. Select Revoke my access at any time; administrators and DoiT staff can see who has authorized a server, but never the tokens themselves.
Using connected tools
Once a server is connected and you are authorized, ask the assistant naturally, for example:
Is there already a Linear issue about yesterday's EKS anomaly? If not, open one for the platform team.
The assistant picks connected tools when they are relevant, exactly as it picks its built-in tools. Before it runs a write action it shows the request and waits for your confirmation. Anything a connected server returns is treated as data: the assistant never follows instructions found inside a tool result.
What is shared and stored
- Sent to the server: the arguments of each tool call, generated by the assistant from your conversation. Internal DoiT notes and cloud credentials are never sent.
- Stored by DoiT: the server's URL and tool definitions, the tool settings your administrators chose, and each user's OAuth tokens (in Google Secret Manager, never in the console database). Revoking your access deletes your tokens.