Setup and authentication
Connect your AI assistant to GuruSup Brain by copying one prompt or following the steps for your client, then check that it works.
Any member of the organization can connect an assistant. You need an assistant that supports MCP. The quickest way is to copy one prompt from Brain and paste it into your assistant. If your assistant cannot change its own settings, follow the manual steps for your client instead. See the MCP overview for what the assistant gets.
Before you start
- You have an account in a Brain organization. Members and admins can both connect.
- Brain answers company questions only once an admin has built the organization's memory. You can connect before that, but the assistant will say Brain is not ready. Members cannot build the memory. An admin does it from the home page of Brain. See the Quickstart.
- You know which assistant you use. The table below shows the routes each one has.
- If you are an admin setting up the organization, the last step of setup, How will you talk to Brain?, has one card for each client: Claude Desktop, Claude Code, Codex, ChatGPT, Cursor, VS Code and Other MCP client. Click the plug button (Connect with the client name) to open a dialog with the tabs Quick and Manual. Quick is there for Cursor and VS Code (Add to Cursor, Add to VS Code) and for Claude Code and Codex (a one-line command with Copy). Manual has the steps and the configuration. Each ends with "Then sign in to Brain when (client) asks." Finish is always on, so you can also connect later from Brain MCP.
Choose your route
| Client | Paste the prompt | Manual steps | One-click link |
|---|---|---|---|
| Claude (desktop app) | No. It cannot edit its own settings. | Claude: add a custom connector | No |
| Claude Code | Yes | Claude Code: one terminal command | No |
| Codex | Yes | Codex: one terminal command | No |
| Cursor | Yes | Cursor: edit mcp.json | Yes |
| ChatGPT (desktop app) | No. It cannot edit its own settings. | ChatGPT: add an MCP server | No |
| VS Code | See below | On the Brain MCP page | Yes |
Restarts differ by client.
| Client | Restart needed? |
|---|---|
| Claude Code | Start or restart it, then run /mcp to check |
| Codex | Start or restart it, then run /mcp to check |
| ChatGPT | Yes. Save, then restart ChatGPT |
| Cursor | No. Cursor detects the change when you save mcp.json |
| Claude | The steps do not ask for one |
| VS Code | The steps do not ask for one. Click Start above the server entry if it does not connect on its own |
VS Code
VS Code is listed on the Brain MCP page, but Brain has no separate page for it here. Open Brain MCP, pick VS Code under Need help setting it up?, and follow the steps shown. They use MCP: Add Server in the Command Palette and a .vscode/mcp.json file in your project. Its snippet uses a top-level servers key, where Cursor's uses mcpServers, so do not paste one client's snippet into the other. For the instruction that makes VS Code use Brain, the page names .github/copilot-instructions.md at the root of your project folder. It also links VS Code's own guides.
Connect with the prompt
Open the Brain MCP page
In GuruSup Brain, click Brain MCP in the sidebar. The page is called Connect your agent. Members and admins both see it.
Copy the prompt
Click Copy prompt. Brain confirms with "Prompt copied." If your browser blocks copying, Brain says "Could not copy. Select the text and copy it by hand."
The prompt already contains the address of Brain's server, so copy it from this page instead of typing anything yourself.
Paste it into your assistant
Paste the prompt into a new conversation with your assistant and send it. It asks the assistant to:
- add the GuruSup Brain server as a remote MCP server over HTTP, under the name
gurusup-brain, - restart itself if its setup needs it, then confirm the server shows as connected and that it can list the server's tools,
- save a short instruction in its long-term instructions, so it checks Brain before answering questions about your company in every future session,
- optionally add Brain's read-only documentation server,
gurusup-brain-docs, which needs no sign-in. The assistant uses it only to learn how to configure and operate Brain, never to answer questions about your company.
Sign in in your browser
Your assistant may open a browser window the first time it connects. If it does, sign in to GuruSup Brain there. If you belong to more than one organization, you choose the organization at this step. After you sign in, the assistant reconnects on its own.
The prompt works best in assistants that can edit their own settings, such as Claude Code, Codex and Cursor. An assistant you use through an app, such as Claude and ChatGPT, cannot change its own configuration from a chat, so use the manual steps for those.
What the saved instruction says
The prompt asks the assistant to keep this instruction in its long-term instructions:
For anything about this company, use the GuruSup Brain 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.
Without it, an assistant can reach Brain but has no reason to. The instruction is short on purpose. The detailed rules arrive when the assistant calls init. See How the assistant is told to behave.
Connect by hand
Open the Brain MCP page and pick your client under Need help setting it up?. Brain shows numbered steps, a snippet you can copy, and a link to the client's own guide. If you pick a client that has one, it also shows an Install GuruSup Brain directly in link.
| Client | Where the steps live |
|---|---|
| Claude | Claude |
| Claude Code | Claude Code |
| ChatGPT | ChatGPT |
| Cursor | Cursor |
| Codex | Codex |
The manual snippets always use the same server name, gurusup-brain. Keep it.
Any other assistant
Brain uses the MCP standard, so any assistant that supports remote MCP servers over HTTP can connect. Add a remote server named gurusup-brain, using the address inside the prompt on the Brain MCP page. When the assistant asks you to sign in, do it in the browser. The server refuses requests that are not signed in.
Then add the same instruction the prompt saves, wherever your assistant keeps long-term instructions.
Check that it works
Check the server
The assistant should tell you the gurusup-brain server is connected and list its tools. If it does not say, ask it: "Is the gurusup-brain server connected?"
Check the tools
A full connection lists 13 tools: init, health, get_profile, start_company_memory_activity, ask_company_memory, search_company_memory, retrieve_company_memory, add_company_knowledge, report_issue, send_feedback, skills_get, skills_publish and request_human_info. Some clients show friendlier titles, such as "Ask Company Memory".
Ask a real question
Ask something your organization's content can answer. A working connection looks like this: the assistant asks Brain, and the answer cites pages Brain returned. If nothing matches, the assistant says it found nothing instead of guessing. See Ask questions.
If the assistant says Brain is not ready to answer company questions yet, the memory has not been built. Ask an admin to check, then try again.
More than one organization or account
Sign-in ties a connection to one person in one organization. If you belong to several organizations, you choose the organization when you sign in, and everything the assistant does through that connection is for that organization only. To work in a different organization, connect again and choose that organization at sign-in.
To see which account a connection uses, ask the assistant to call get_profile. It returns your email and an opaque profile ID that stays the same for you in that organization. ChatGPT uses this tool to label connected accounts and tell them apart. See ChatGPT.
If something goes wrong
Look in your assistant's list of connected servers or tools. If gurusup-brain is missing or not connected, paste the prompt again, or follow the manual steps for your client. For sign-in problems, wrong-organization problems and error messages, see MCP troubleshooting. To see what an assistant can access, see What an agent can see.