Cortex MCP reference

Cortex exposes one hosted remote HTTP MCP server for knowledge and coordinated work.

Endpoint

Use this canonical server URL:

https://cortex.socra.cloud/mcp

The server does not require a local process or a local MCP passthrough.

Discovery

An unauthenticated request receives a 401 Bearer challenge with a resource_metadata URL. The canonical protected-resource metadata is available at:

https://cortex.socra.cloud/.well-known/oauth-protected-resource/mcp

The metadata identifies https://oauth.socra.cloud as the authorization server. OAuth discovery directs browser authorization to https://account.socra.com/oauth/authorize and token requests to https://oauth.socra.cloud/oauth/token.

Authorization

First-party coding-agent plugins use pre-registered public clients and Authorization Code with PKCE. Custom applications register an OAuth client through a customer-owned Cloud Project.

Cortex accepts the standard account-scoped Socra access token. It does not require a separate Cortex-only audience token.

Tool families

The MCP server presents tools from these Cortex areas:

• context_* tools inspect the knowledge map and flash Modules.
• issue_* tools inspect and coordinate work.
• comment_* tools read and author Issue discussion.

The discovered tool schema is the current interface reference. Review it in the host before allowing writes or deletes.

Custom configuration

Follow Configure the Cortex MCP server to register and connect a custom client.