Cortex MCP Server
Connect Cortex to your AI agents with the Cortex MCP server.
Updated
What is Cortex MCP?
The Cortex MCP server is a Model Context Protocol server that connects Cortex to AI agents and assistants as a set of tools. With it connected, an agent can work with Cortex (internal developer portal) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses a bearer token, so you point your client at the server URL, authorize once, and the Cortex tools become available to the model.
Connect the Cortex MCP server
Connect Cortex MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Cortex MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (a bearer token) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Cortex tool to confirm the connection is live.
Connect Cortex MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Cortex
Provide the Cortex MCP server URL or command and complete authentication.
- 3
Test
Reference Cortex from chat to confirm Cursor can reach the tools.
Using Cortex MCP with Gamut
On Gamut, the Cortex MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Cortex and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Cortex MCP server?
It is a Model Context Protocol server that exposes Cortex to AI agents as tools so they can work with it (internal developer portal).
How do I connect the Cortex MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Cortex MCP server URL and complete authentication (a bearer token). See the official documentation for the exact URL and scopes.
Can I use Cortex MCP with Gamut?
Yes — Gamut supports the Cortex MCP server, so your agents can use it as a tool in automated, triggered workflows.