MCP Server
Overview
Atolio includes a remote Model Context Protocol (MCP) server, letting the AI assistants and agents your teams already use search across your company’s apps through Atolio.
Every request is made on behalf of the signed-in user. Just like Atolio itself, the MCP server never surfaces information that the user doesn’t have access to, honoring the permission model of the underlying apps that are integrated.
Available Tools
The MCP server offers the following tools to connected clients:
| Tool | Description | Parameters |
|---|---|---|
search-agent | Searches your organization’s connected knowledge (documents, messages, tickets) and returns a synthesized plain-text answer. |
|
grep | Reads the content of one or more documents by their atd_ prefixed document ID, such as those referenced by search-agent. Provide a pattern to return only matching lines rather than the full document. |
|
A typical flow is for the assistant to ask search-agent a question, then use grep to read the documents behind the answer in more detail.
Enabling the MCP Server
The MCP server is part of every Atolio deployment, and relies on the authentication already configured for your deployment. Access is denied by default: an MCP client can only obtain access on behalf of a user once it has been approved.
To enable access, reach out to the Atolio team with:
- The MCP clients your organization would like to use (e.g. Claude Code, Cursor)
- The users who should be able to connect to them (or broad access, if desired)
The Atolio team will guide your deployment engineer on the necessary steps or action it through an existing client support mechanism.
Connecting a Client
Once access is enabled, add Atolio to your MCP client using your MCP endpoint URL. The first time the client connects, it will open a browser window for you to sign in to Atolio. After signing in, the client receives a token scoped to the MCP server and requests are made on your behalf.
The examples below use https://search.example.com, replace it with your Atolio deployment URL.
Claude Code
claude mcp add --transport http atolio https://search.example.com/api/mcp
Then run /mcp within Claude Code and select atolio to sign in.
Claude Desktop & Claude.ai
- Open Settings and select Connectors.
- Select Add custom connector.
- Enter
Atolioas the name, and your MCP endpoint URL as the URL. - Select Connect and sign in to Atolio.
Cursor
Add the following to ~/.cursor/mcp.json:
{
"mcpServers": {
"atolio": {
"url": "https://search.example.com/api/mcp"
}
}
}
Codex
codex mcp add atolio --url https://search.example.com/api/mcp
Then run codex mcp login atolio to sign in.
IBM Bob
Add the following to .bob/mcp.json in your project, or to ~/.bob/settings/mcp.json to make it available across all workspaces:
{
"mcpServers": {
"atolio": {
"type": "streamable-http",
"url": "https://search.example.com/api/mcp"
}
}
}
Bob will prompt you to sign in from the MCP tab of its settings.
VS Code
Add the following to .vscode/mcp.json in your workspace:
{
"servers": {
"atolio": {
"type": "http",
"url": "https://search.example.com/api/mcp"
}
}
}
Other Clients
Any MCP client supporting the Streamable HTTP transport and OAuth authorization can connect to Atolio. Clients discover the authorization server automatically from the endpoint, using the following metadata:
- Protected resource metadata:
https://search.example.com/.well-known/oauth-protected-resource/api/mcp - Authorization server metadata:
https://search.example.com/.well-known/oauth-authorization-server
Atolio supports both Client ID Metadata Documents and Dynamic Client Registration for identifying clients.