Skip to main content
Cortex connects over the Model Context Protocol (MCP), an open standard for giving AI tools access to external systems. Any MCP-capable client can connect to Cortex, not just the ones with their own guide.

​
The general shape

Every Cortex connection works the same way:
  1. The endpoint is your workspace’s URL, https://api.oncortex.ai/t/your-workspace-id/mcp, shown on any brain’s Connect page under the generic tab. It uses the standard streamable HTTP transport.
  2. Sign-in is automatic. Cortex advertises how to authenticate using standard MCP discovery, so a client with sign-in support will send you to Cortex to approve, then connect itself. There are no API keys to paste for interactive use.
  3. The connection acts as you. It reaches every brain you can access in the workspace, at your roles, checked live on every call.

​
Cursor

Cursor supports MCP servers in its settings. Add a new MCP server using the Cortex connection URL from the Connect page. When Cursor first uses it, approve the connection in the browser. After that, Cursor can search and file across your brains.

​
Anything else

For any other MCP client, the recipe is the same: give it the connection URL, let it walk you through the browser approval, and you are connected. If your client cannot do the browser sign-in step (for example an automated script or a server with no human present), use a service credential instead.

​
Compatibility

MCP client support is moving quickly. The reliable test is simple: if your tool can add a remote or custom MCP connector by URL and supports sign-in, it works with Cortex. If it can only use static keys, connect it as an automation with a service credential.