MCP Preview

Codatum provides an MCP (Model Context Protocol) server. By connecting MCP clients such as Claude and Cursor, you can run the AI agent from those clients.

INFO

This feature is in preview. To request access, contact Codatum support.

AI agent runs use the permissions of the connected user.

From global nav > Workspace settings > MCP, you can check the MCP URL and manage connections.

Connecting

1. In Workspace settings > MCP, copy the MCP URL.
2. Add the MCP URL to your MCP client. For how to add it, see the documentation of your MCP client.
3. The MCP client opens the Codatum authorization page in your browser. Sign in and select the Workspace to connect.
4. Review the scopes under Permissions requested and select Authorize.

After approval, the connection appears in the connection list.

A connection is created for each combination of user and workspace. To connect to another workspace, authorize again.

Authorization uses OAuth (authorization code flow with PKCE). No client pre-registration is required; Dynamic Client Registration and Client ID Metadata Documents are supported.

Scopes

Scopes define the operations the connected MCP client can perform. The authorization page shows the requested scopes, and only the approved scopes are granted to the connection.

Scope	Description
agent:execute	Create and run AI agent sessions in the connected workspace and read their results.

Available tools

The connected MCP client can use the following tools. All of them require the agent:execute scope.

Tool	Description
list_ai_profiles	Lists the available AI profiles.
send_message	Sends a message to an agent session. If the session ID is omitted, a new session is created.
get_agent_session	Gets the session status, messages, pending approvals, and the session URL in Codatum.
respond_to_approval	Approves or rejects a pending tool execution.
abort_agent_session	Aborts a running session.

When an agent action is pending approval (for example, an operation with Auto-approve Tool Execution turned off in user settings), you can approve or reject it from the MCP client. You can also open the session in Codatum.

Connection list

Each user can view their own connections. Switching to All connections can be performed by a Workspace Owner (Workspace permissions).

Column	Description
Client	The name of the connected MCP client
Connected by	The user who made the connection (shown only in All connections)
Scopes	The operations the connection is allowed to perform (Scopes)
Connected	When the authorization was approved
Last used	When the connection was last used

Disconnecting

Select Disconnect to revoke the authorization. The client can no longer access the workspace and must be authorized again to reconnect. You can disconnect your own connections. A Workspace Owner can disconnect any connection in the workspace.