Coro provides a standard MCP (Model Context Protocol) server to enable organizations to connect their AI services to Coro's secure data repositories. This means that AI agents can query and act on security data and configuration in connected workspaces.
This article describes Coro's MCP server and explains what functionality it provides.
An MCP server is an industry-standard, secure intermediary between an organization's AI tools and Coro's workspace security data. It provides a consistent, controlled way for AI agents to query and interact with workspace data without requiring direct access or custom integration.
You link your AI tools directly to a single MCP server endpoint that manages request validation, authentication, and routing. This guarantees that all interactions are secure, auditable, and subject to established policies for data access.
This approach abstracts the complexity of Coro's internal systems and provides a stable interface for external AI integrations.
Admin users create a connection between their AI client and Coro's MCP server as a Connector or App (depending on AI client vendor terminology), enabling requests and instructions made through the client to be directed at the Coro MCP server.
Requests can be based against a series of published tools. For example, if Coro publishes a tool called list_workspaces, a request prompt can include an instruction like show me a list of my workspaces. The AI client recognizes that this request matches one or more available tools and can send the request to the MCP server.
When an AI agent sends a request:
- The request is sent to the Coro's MCP server endpoint.
- The MCP server authenticates and validates the request.
- The server translates the request into one or more calls to Coro's underlying public REST API.
- The response is normalized and returned to the AI agent as a structured JSON response object.
Your AI agent should be configured to translate the JSON response into a human readable format. This is outside the scope of Coro's MCP server.
Coro authenticates connection requests from an AI client against an existing user account in the Coro console. To establish a connection to the MCP server, your account must be an applicable admin user role in at least one workspace.
Applicable roles are:
- Workspace administrator
- Workspace super admin
- MSP administrator
- MSP super admin
Your requests are processed against all workspaces for which you have an administrator or super admin role.
To connect to Coro's MCP server, use the following endpoint URLs depending on your workspace region:
https://api.secure-ca.coro.net/mcp- Canadahttps://api.secure-eu.coro.net/mcp- European Unionhttps://api.secure.coro.net/mcp- United States
Coro's supports connections from all AI clients that have the capability to connect to standard MCP endpoints.
This section offers two examples of app or browser-based connections, one from ChatGPT and another from Claude AI, along with an example of connecting through a command-line tool.
Coro endeavors to keep these instructions up to date. However, it has no control over changes to external software. These instructions are provided as examples of current practice and without any warranty regarding their future suitability.
To connect via ChatGPT:
Make sure your ChatGPT subscription allows connections to custom unverified apps.
Sign in to the Coro console in your web browser as as admin user with an applicable role.
Sign into ChatGPT in a web browser or through the desktop app.
From the sidebar, select Plugins:

From the Plugins page, select Add > Add custom MCP server:

If Add custom MCP server is not an available option, you may not have permissions to perform this operation. Contact your account administrator.
ChatGPT displays the Add custom MCP server dialog:

Enter the following details:
- Name: Enter a name for the MCP Server app.
- Description: (Optional) Enter a description for the app.
- Connection: Select Server URL, then enter the Coro MCP Server URL that corresponds to the region containing your workspaces.
- Authentication: Select OAuth.
Read and accept the notice about custom MCP servers, then select Create as a plugin.
ChatGPT creates the new plugin and presents a connection dialog.
Select the connect button:

ChatGPT redirects you to Coro to authenticate the access request for your Coro account.
Coro displays the access confirmation dialog:

MSP admin users with responsibility for multiple child workspaces can select the scope of the plugin's access:

Select Regular Admin to connect ChatGPT with your currently signed-in workspace.
Select Global Admin to connect ChatGPT with access to all of your available workspaces.
Review the access request, then select ALLOW.
Coro redirects you back to ChatGPT, showing the new plugin within your Personal collection:

To connect via Claude AI:
Make sure your Claude AI subscription allows you to create custom connectors.
Sign in to the Coro console in your web browser as as admin user with an applicable role.
Sign in to Claude AI in a web browser or through the desktop app.
From the menu bar, select your user avatar. From the menu, select Settings:

Select Connectors, then locate and select Add custom connector:

If Add custom connectors is not an available option, you may not have permissions to perform this operation. Contact your account administrator.
Claude displays the Add custom connector dialog:

Enter the following details:
- Name: Enter a name for the connector.
- Remote MCP server URL: Enter the Coro MCP Server URL that corresponds to the region containing your workspaces.
Select Continue.
Claude displays the authentication selector dialog:

Coro recommends accepting the default settings. Select Add.
Claude creates the connector.
Select Connect:

Claude redirects you to Coro to authenticate the access request for your Coro account.
Coro displays the access confirmation dialog:

MSP admin users with responsibility for multiple child workspaces can select the scope of the connector's access:

Select Regular Admin to connect Claude with your currently signed-in workspace.
Select Global Admin to connect Claude with access to all of your available workspaces.
Review the access request, then select ALLOW. Coro redirects you back to Claude, showing the connection as successful:

Configure your AI command-line tool with the following MCP server definition:
"coro": {
"url": "https://api.<region>.coro.net/mcp",
"type": "http",
}Use the URL that corresponds to your workspace region. For details, see Authenticating with Coro.
After you have saved this definition to your MCP server list file, instruct the tool to authenticate the connection. The process for this varies by tool.
For example, using Claude Code:
Sign in to the Coro console in your web browser as as admin user with an applicable role.
From the Claude Code command line, enter
/mcpat the prompt to manage your MCP servers:
Select the Coro MCP server:

Select Authenticate:

Claude Code redirects you to Coro to authenticate the access request for your Coro account.
Coro displays the access confirmation dialog:

MSP admin users with responsibility for multiple child workspaces can select the scope of the connection's access:

Select Regular Admin to connect Claude with your currently signed-in workspace.
Select Global Admin to connect Claude with access to all of your available workspaces.
Review the access request, then select ALLOW. Coro redirects you back to Claude Code, showing the connection as successful:

After you connect Coro's MCP server to an AI agent, it may be necessary to check that the agent has full access to the relevant workspace data and pubished tool set.
Following connection, Coro recommends entering a simple prompt to verify access and test the scope. For example:
list my workspaces
You can also ask the agent to show the list of available tools:
show me the tools available
Some agents may list the tools within the connector/plugin configuration. For example, in Claude, select your Coro MCP connector from the Settings > Connectors page to view a complete list.
From time to time, Coro may update the list of tools available to AI agents in line with our standard release protocol for new features and product enhancements.
To ensure your agent is using the most up-to-date tools, it might be necessary to refresh the tool list.
For ChatGPT, select the Coro MCP plugin, then select Manage. Locate the Manage app section and select Refresh tools:

For Claude, go to Settings > Connectors and select the Coro MCP connector. Select the three-dot menu icon, then select Refresh tools list:

In these agents, as with others, an alternative method is to uninstall the plugin/connector and then reconnect.
Coro's MCP server supports the following tools for connected AI clients:
| Tool | Description |
|---|---|
| list_workspaces | List all accessible workspaces. |
| get_workspace | Get full workspace details. |
| create_workspace | Create a new child workspace. |
| search_workspaces | Search workspaces by name/domain/ID. |
| update_workspace | Change the editable details of a workspace. |
| Tool | Description |
|---|---|
| get_subscription | Get subscription state and active modules. |
| start_subscription | Activate a workspace subscription. |
| stop_subscription | Freeze a workspace subscription. |
| update_subscription | Update which modules, add-ons, and bundles are active on a workspace’s subscription. |
| get_bundle_info | Get details of specific bundles. |
| get_usage | Get billing usage data for a time range. |
| Tool | Description |
|---|---|
| list_tickets | List security tickets with filters. |
| get_ticket | Get detailed ticket information. |
| get_ticket_actions | Get available actions for a ticket. |
| perform_ticket_action | Execute an action on a ticket. |
| list_ticket_comments | List the comments added to a ticket. |
| add_ticket_comment | Add a comment to a ticket as the currently authenticated admin user. |
| get_tickets_summary_devices | Aggregate device ticket summary. |
| get_tickets_summary_users | Aggregate user ticket summary. |
| get_tickets_summary_emails | Aggregate email ticket summary. |
| get_tickets_summary_cloud_apps | Aggregate cloud application ticket summary. |
| get_tickets_summary_data | Aggregate data governance ticket summary. |
| Tool | Description |
|---|---|
| list_devices | List protected devices. |
| get_device_actions | Get available actions for a device. |
| perform_device_action | Execute an action on a device. |
| get_latest_agent_versions | Get latest agent versions per platform. |
| Tool | Description |
|---|---|
| list_users | List protected end-users. |
| get_user | Get protected user details. |
| add_users | Add users for protection (up to 200). |
| update_user | Update user details/protection status. |
| delete_user | Remove a user from protection. |
| Tool | Description |
|---|---|
| list_portal_users | List admin console users. |
| get_portal_user | Get admin user details. |
| add_portal_user | Add a new admin portal user. |
| Tool | Description |
|---|---|
| search_audit_logs | Search audit logs with filters. |