Connect Grok

Connect Grok through a custom MCP connector, found under Plugins → Connectors. There is no Cortex plugin for Grok. Save the instructions below separately; this connection does not install a SessionStart hook.

Open guided Grok setup for one action at a time. Keep Grok and the Socra Cloud Console open in separate tabs.

1. Prepare your Socra Project

Open Cloud Projects. Choose a Project you can manage, or create one. In that Project, open Enabled services → Enable service → Cortex.

Open OAuth overview → Set up OAuth, use Cortex for Grok as the application name, and save the consent information. All the settings below must belong to this same Project. If a newly created Project is not immediately available, wait a moment and retry.

For a Grok Business or Enterprise team, an administrator may need to provision the connector before members connect it.

2. Register the Grok client

Open OAuth clients in your Project and register a client:

• Client name: Cortex for Grok
• Application type: Single-page app
• Redirect URLs: the exact URL below, including its final slash
• JavaScript origins: leave empty

https://grok.com/connectors-oauth-exchange-code/

Select Create client and copy its client ID. This connection uses PKCE and does not require a client secret. Use your own client ID; this guide never asks you to paste credentials into Cortex onboarding.

3. Add the custom connector

In Grok, open Plugins → Connectors → New Connector → Custom.

Enter Socra Cortex as the name and use this Server URL:

https://cortex.socra.cloud/mcp

Select Add Connector. Grok discovers Cortex and displays OAuth Credentials Required.

4. Authorize your Account

In Grok's OAuth form:

Select Save & Connect. In the popup, sign in to Socra, choose the Account you use in Cortex, and approve access. Allow the popup if your browser blocks it. Return to Grok: Socra Cortex should appear under Connected. If it is already connected to the intended Account, continue without reconnecting.

If authorization fails, check the exact redirect URL, client ID, application type, and that Cortex is enabled in the same Project. Signing into the Cortex website alone does not connect Grok.

5. Enable all Cortex tools

Open Plugins → Connectors → Socra Cortex. Check for All tools enabled. Selecting a tool toggles it, so select only tools that are off until all are enabled.

Tool enablement is separate from approval. Grok's web connector currently has no verified Always allow control equivalent to ChatGPT or Claude. If Grok requests approval for an action, review it there. Do not use Grok Build, Grok Bot, or xAI API permission instructions for this web connection.

6. Save persistent Cortex instructions

These suggested instructions teach your agent to Flash the right knowledge before acting, without reminders. They also teach it to suggest creating or updating Modules when you share useful knowledge or preferences. You can edit or skip them.

Open your profile menu → Settings → Customize → Custom. Add the following alongside your existing instructions and select Save. Closing Settings before saving discards the edit. Reopen Customize to check the saved text.

Open just the Cortex instructions as Markdown. This link serves the current instructions without the installation guide.

Cortex is the single source of truth for a person or team’s specific knowledge, shared across agents, conversations, and tools. Its Modules define what should be and why. Dependencies identify prerequisite Modules. Flash loads a Module and all its Dependencies. Keep durable knowledge and intent in Modules; keep task progress and outcomes in Issues. Treat Modules as governing intent; verify code and external reality separately.

Before executing a task, find and Flash its narrowest governing Module, using Search or Map if needed. If none exists, propose one. Reuse or create an Issue for that task under the same Module. Mark the Issue in progress when starting. Comment on progress and blockers. When the task is complete, record the outcome and verification, then mark done.

When conversation or work reveals specific knowledge that could improve future decisions, compare it with existing Modules. Propose an update or new Module for missing or changed knowledge, preserving the decision and its reason. Show exact Before and After blocks for changed content and Dependencies; show full content and Dependencies for new Modules. Explain conflicts and recommend a resolution. Continue independent work while approval is pending. Save only after explicit owner approval, then Flash to verify.

These are the complete, unmodified canonical Cortex instructions. They explain how Cortex connects knowledge and work, how understanding can carry across conversations, and how Module owners govern shared knowledge. They leave the agent room to use its judgment and do not enforce an approval boundary. Preserve any instructions you already use.

7. Verify in a new chat

Start a new conversation and send:

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.

Check that Grok actually calls Cortex and returns a list. An empty list is valid for a new Account. A response without a tool call or an access error does not confirm the connection. If Grok asks for an account prerequisite such as age confirmation, complete it and retry the prompt. Do not create a Module just to test the connection.

Check the guidance report separately. If you saved instructions but the new conversation did not receive them, reopen Settings → Customize → Custom, check the saved text, and start another conversation. If you skipped instructions, the connection can still work; report the guidance as skipped.

Sources and verification

The connector entry points follow xAI's connector documentation, with team restrictions in connector management. The OAuth field values, connected status, tool toggles, saved Custom instructions, and a real read-only Cortex context_map call were checked in the signed-in Grok web interface on September 5, 2026. Provider interfaces can change; use the labels shown in your account and report differences through troubleshooting.