Skip to content

Configure the Cortex MCP server

View as Markdown

Connect ChatGPT, Claude, or another MCP client to Cortex. Use this guide when you set up the connection yourself.

The integration uses the hosted Cortex MCP server. You do not need to install a server on your computer.

An MCP integration provides Cortex tools but does not install the guidance included with a Cortex agent plugin. If you use a supported coding agent, follow Agent plugins instead.

Open guided MCP setup (new tab) to follow these instructions one step at a time. For the preferred ChatGPT store installation, use Connect ChatGPT. Grok uses a different, secret-free PKCE flow: follow Connect Grok.

Before you start

You need an Account and a Cloud Project that you can manage. If you do not have one, create a Cloud Project in the Cloud Console at platform.socra.com.

Your client must support remote HTTP MCP and follow the resource_metadata URL in Cortex's 401 OAuth challenge. Test the connection in your host. Use the CLI if the host cannot connect.

The hosted MCP surface includes tools that can write and delete. Review the Cortex security model and your client's approval policy before you connect. Review the discovered tools before you enable them in a conversation.

Set up the integration

Enable Cortex and configure OAuth on your Cloud Project. Then connect your MCP client.

Enable Cortex

Cloud Console

In the Cloud Console, open Enabled services. Select Enable service, then enable Cortex for the Cloud Project.

Configure OAuth

Configure the information that Socra shows when a user authorizes the integration.

Cloud Console

In the Cloud Console, open OAuth overview. Select Set up OAuth. Use Cortex as the application name. Add any policy information that users should see during authorization.

Configure your MCP client

Select the client that you want to connect to the Cortex MCP server.

Custom

Register an OAuth client

Start the custom MCP setup in your client. Find the OAuth callback URL that the client provides.

In the Cloud Console, open OAuth clients. Register a Web client. Add the callback URL as a redirect URL. Leave JavaScript origins empty.

Create the OAuth client. Then create a client secret. Copy the secret immediately. Socra shows it one time.

Connect your client

Enter these values in your MCP client:

  • Name: Cortex
  • Server URL: https://cortex.socra.cloud/mcp
  • Authentication: OAuth
  • Client ID: The OAuth client ID from Socra
  • Client secret: The OAuth client secret from Socra

Connect your Account and approve access.

Enable Cortex tools

In ChatGPT, open Settings → Plugins → Socra Cortex and select Permission. In Permissions, select Allow all tools (or Allow all actions, if shown) for Cortex. A custom connector may be named Cortex.

In Claude, open Settings → Connectors → Cortex → Tool permissions. Set both Read-only tools and Write/delete tools to Always allow. In a new chat, check that Cortex is on under + → Connectors.

In another client, enable all Cortex tools and use its Cortex-scoped always-allow setting if available. These controls vary by host and organization policy. Keep unrelated permissions unchanged. The suggested instructions teach the agent to maintain useful knowledge and tell you what changed and why.

For Grok's different controls and PKCE connection, follow Connect Grok.

Add persistent instructions

Add the suggested Cortex instructions to teach your agent to Flash the right knowledge before acting and create or update Modules when you share useful knowledge or preferences. A direct MCP connection needs these saved separately. You can edit or skip them. In Claude, use Settings → Account → Instructions for Claude. In other clients, use their persistent or project instructions. Keep existing instructions.

Verify the connection

Start a new conversation with Cortex enabled. Use this prompt:

Text
Use Cortex to list the Modules I can access. Make a real Cortex tool call; an empty list is valid. Separately, report whether this new conversation received persistent Cortex guidance and what it requires. Do not change anything.

Verify that the agent makes a real Cortex call and returns a Module list. An empty list confirms access for a new Account. An error or an answer without a tool call does not confirm the connection.

Check the guidance report separately. If you saved instructions but the new conversation did not receive them, check their saved location and scope in the host. Start the conversation inside the project if you used project instructions. If you skipped instructions, the connection can still work; report the guidance as skipped.

Stop after verification. When you are ready to use Cortex, follow the Cortex Quickstart.

See also