Codex
Connect Gurusup to the Codex CLI by installing its plugin with one terminal command, and make Codex use it whenever you ask about your company.
For any member of a Gurusup organization. The steps on the Gurusup MCP page cover the CLI only.
This page covers the one-command route that the Gurusup MCP page shows. To let Codex add the server from a pasted prompt instead, see Setup and authentication.
Before you start
- You have an account in a Gurusup organization.
- The Codex CLI is installed. Run
codex --versionin a terminal to check. If it fails, install Codex first. - You have the command. Open Gurusup MCP in the Gurusup sidebar and click the plug button (Connect Codex) on the Codex card, "Install the plugin with one command." The dialog opens on Quick with the command and a Copy button.
Connect Codex
Open a terminal
Any terminal works.
Run the command
Run the command exactly as shown. It installs the Gurusup plugin from OpenAI's catalog:
codex plugin add gurusup-brain@openai-curated-remote
Restart and sign in
Start or restart Codex, then run /mcp. gurusup-brain shows up in the list. Sign in to Gurusup when Codex asks: a sign-in page opens in your browser, so use the account you use for Gurusup. If you belong to more than one organization, choose it at this step.
The Manual tab of the dialog lists the same steps.
Alternative: add only the server
If you prefer to add the Gurusup server without the plugin, use Codex's own command. The Gurusup MCP page does not show it, but the server is a plain remote MCP server over HTTP:
codex mcp add gurusup-brain --url https://mcp.brain.gurusup.com/mcp
Keep the name gurusup-brain. The command writes the connection into ~/.codex/config.toml, so you do not edit that file by hand. That file is your user-wide Codex configuration, so Gurusup is available in every project you open with Codex. OpenAI's guide says you can also scope a server to one project with a .codex/config.toml file, but this command does not do that. For more detail, see the Codex MCP guide.
The same guide says the ChatGPT desktop app, the Codex CLI and the Codex IDE extension share this configuration, so a server you add this way can show up in the others. See ChatGPT.
Save the instruction
Open AGENTS.md at the root of your project, or create it. Paste this instruction and save: "For anything about this company, use the Gurusup tools before answering. Call init first, then ask_company_memory. Answer only from what those tools return, and if they find nothing, say so instead of guessing." Codex picks it up on its next run.
An AGENTS.md at the root of a project applies to that project. The instruction only reaches Codex in projects that have it.
Check that it worked
Check the server
Run /mcp in Codex. gurusup-brain shows up in the list, signed in. If you added only the server, codex mcp list outside Codex shows it too.
Check the tools
Ask Codex: "Which tools do you have from gurusup-brain?" It lists 13, starting with init and ask_company_memory. See the Tools reference.
Ask a question that needs two sources
Ask something only your joined sources can answer. With Linear and Slack connected, for example: "Which open Linear issues block the next release, and what did the team decide about them in Slack?" Codex asks Gurusup and answers from what it returns. See Ask questions.
If it does not work
| What you see | What to do |
|---|---|
gurusup-brain is missing from /mcp | Run the install command again and restart Codex. If you added only the server, check that you kept the name gurusup-brain. |
| The server is listed but not signed in | Run /mcp and sign in. If you added only the server, codex mcp login gurusup-brain also works. |
| Codex connects but does not use Gurusup | Check that AGENTS.md in this project holds the instruction |
For anything else, see MCP troubleshooting.