Claude Code

Connect GuruSup Brain to Claude Code with one terminal command, and make it use Brain.

Use this page to connect GuruSup Brain to Claude Code. It takes one command.

If you would rather paste a prompt and let Claude Code do it, see Setup and authentication. The steps below are the manual route.

Before you start

You have an account in a Brain organization.
The Claude Code CLI is installed. Run claude --version in a terminal to check. If it fails, install Claude Code first.
You have the command with the Brain MCP URL. Open Brain MCP in the Brain sidebar and pick Claude Code under Need help setting it up?. The Terminal box shows the command, ready to copy.

Connect

Open a terminal

On macOS, use the Terminal app. On Windows, use PowerShell or WSL. Go to the project folder where you use Claude Code (see the scope note below).

Run the command

Run the command exactly as shown. In production it looks like this. If the Brain MCP page shows a different URL, use that one:

claude mcp add --transport http gurusup-brain https://mcp.brain.gurusup.com/mcp

Keep the name gurusup-brain. It is what identifies Brain in Claude Code. Press Enter. Claude Code confirms the server was added.

Restart and check

Start or restart Claude Code. Run /mcp inside it. gurusup-brain should show as connected.

If a sign-in page opens in your browser, sign in with the account you use for Brain. If you belong to more than one organization, you choose the organization at this step.

For more detail, see the Claude Code MCP guide.

Scope: where the server is available

The command as Brain shows it does not set a scope. Claude Code's documentation says the -s or --scope flag decides where the configuration is stored:

Scope	Where the server is available
`local` (the default)	Only to you, in the current project
`project`	Shared with everyone in the project through the `.mcp.json` file
`user`	To you, across all projects

So with the command above, Brain works in the project you ran it in and not in others. To use Brain in every project, run the command with --scope user:

claude mcp add --scope user --transport http gurusup-brain https://mcp.brain.gurusup.com/mcp

Use project only if the whole team should share the connection through a committed .mcp.json file. Each person still signs in as themselves.

Make Claude Code check Brain

Adding the server gives Claude Code access to Brain. To have it use Brain for company questions, open CLAUDE.md at the root of your project, or create it. Paste this instruction and save: "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." Claude Code reads it at the start of every session in that project.

A CLAUDE.md at the root of one project applies to that project only. If you added the server with --scope user and want the instruction everywhere, save it wherever you keep instructions that apply to all your projects. See Claude Code's memory guide.

Check that it works

Check the server

Run /mcp and look for gurusup-brain as connected. You can also run claude mcp list in a terminal.

Check the tools

Ask Claude Code: "Which tools do you have from gurusup-brain?" A full list has 13, starting with init and ask_company_memory. See the Tools reference.

Ask a question

Ask something your organization's sources can answer.

What success looks like: Claude Code asks Brain and answers from what Brain returns. If Brain has nothing, it says so. See Ask questions.

Claude Code's documentation gives these commands:

/mcp inside Claude Code starts the sign-in for a server that needs it. Follow the steps in your browser.
claude mcp login <name> runs the sign-in from your shell.
claude mcp list shows configured servers, and claude mcp get <name> shows one.
claude mcp remove <name> removes a server. Use gurusup-brain as the name.

To switch organization or account, remove the server and add it again, then sign in and choose the right organization.

If it doesn't work

Run /mcp again and look for gurusup-brain.
Check that you kept the name gurusup-brain and used the URL from the Brain MCP page.
If the server is missing in another project, it was added with the default local scope. Add it with --scope user.
See MCP troubleshooting.

Was this page helpful?