ClientsCursor

Cursor

Connect GuruSup Brain to Cursor with a one-click link or by editing mcp.json, and add the rule that makes Cursor use it.

Use this page to connect GuruSup Brain to Cursor. You can use a one-click link or edit mcp.json yourself.

If you would rather paste a prompt and let Cursor do it, see Setup and authentication.

Before you start

  • You have an account in a Brain organization.
  • You have Cursor installed.
  • Open Brain MCP in the Brain sidebar and pick Cursor under Need help setting it up?. The page shows the one-click link, the steps and an mcp.json box with the JSON to copy.

Option 1: one click

On the Brain MCP page, after you pick Cursor, click Install GuruSup Brain directly in Cursor. This opens Cursor's install link for the gurusup-brain server. Follow what Cursor shows you, then check the result under Tools & MCP.

Option 2: edit mcp.json

Open Tools & MCP

Open Settings. Use the gear icon, or the Cursor menu, then Settings, then Cursor Settings. Click Tools & MCP in the left sidebar.

Open mcp.json

Click New MCP Server. This opens, or creates, your mcp.json file.

Paste the JSON

Paste this inside the file. In production the URL is the one below. If the Brain MCP page shows a different URL, use that one.

{
  "mcpServers": {
    "gurusup-brain": {
      "type": "http",
      "url": "https://mcp.brain.gurusup.com/mcp"
    }
  }
}

If the file already lists other servers, add gurusup-brain next to them. Do not replace the file.

Save

Save the file. Cursor detects the change on its own, so you do not need to restart. gurusup-brain should show as connected in the Tools & MCP list. 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 Cursor MCP guide.

Project or global mcp.json

Cursor's documentation names two places for the file: .cursor/mcp.json in a project, for tools specific to that project, and ~/.cursor/mcp.json in your home directory, for tools available everywhere. Brain works from either. Put it in the global file to use it in every project, or in the project file to use it in one project only. The steps above say New MCP Server opens or creates your mcp.json; check the path Cursor shows to see which one you are editing.

Make Cursor check Brain

Connecting gives Cursor access to Brain. To have it use Brain for company questions, add a rule.

Create the rule file

Create .cursor/rules/gurusup-brain.mdc in your project.

Paste the rule

Paste this into the file and save:

---
description: Use GuruSup Brain for questions about this company
alwaysApply: true
---
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.

The .mdc extension matters: Cursor's documentation says a plain .md file in .cursor/rules is ignored. The frontmatter has three fields: description, globs and alwaysApply. With alwaysApply: true the rule is included in every session, and globs and description are ignored. Without it, Cursor decides when to apply the rule from the description or from matching files, so Brain may not be used for a general question. See Cursor's rules guide.

A rule in .cursor/rules applies to that project only. Add the file to each project where you want Cursor to use Brain.

Check that it works

Check the server

Look for gurusup-brain as connected in the Tools & MCP list.

Check the tools

Ask Cursor: "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: Cursor asks Brain and answers from what Brain returns. See Ask questions.

Turn the server off

Cursor's documentation says you can switch a server off without removing it: open Customize in the sidebar, find the server and use its toggle. A disabled server does not load or appear in chat. To remove it for good, delete the gurusup-brain entry from the mcp.json file it lives in.

If it doesn't work

  • Look for gurusup-brain in the Tools & MCP list, and check that its toggle is on.
  • If you edited mcp.json, check that the JSON is valid and that other servers are still in the file.
  • If Cursor connects but does not use Brain, check that the rule file ends in .mdc and has alwaysApply: true.
  • See MCP troubleshooting.
Was this page helpful?