Connect Cortex to an MCP client

Connect Cortex to an MCP client

Use the remote MCP endpoint:

https://cortex.socra.cloud/mcp

Add that URL as a remote MCP server in your client. Select Streamable HTTP when the client asks for a transport. The server uses account-scoped OAuth. Complete the browser sign-in and consent flow when your client opens it. You do not need to paste a static bearer token.

After connection, your client can discover three tool families:

• Context tools find, read, flash, and maintain modules.
• Issue tools read the inbox and coordinate work.
• Comment tools preserve authored progress on issue timelines.

Start a real task. Let the agent use context_map or context_search when it needs account knowledge. It should call context_flash before acting in a known domain.

A new account has no seeded modules. Empty results are expected until an owner approves the first durable knowledge. The agent must ask for exact approval before it creates or updates a module.

If authentication fails, remove the stale MCP authorization from the client and reconnect. The endpoint returns the OAuth authorization server through its protected-resource metadata.