Cursor
Connect Gurusup to Cursor with a one-click link or by editing mcp.json, and add the rule that makes Cursor use it.
For any member of a Gurusup organization.
To paste a prompt and let Cursor do it, see Setup and authentication.
Before you start
- You have an account in a Gurusup organization.
- Cursor is installed.
- Open Gurusup MCP in the Gurusup sidebar and click the plug button (Connect Cursor) on the Cursor card, "Installs in one click." The dialog has a Quick tab with Add to Cursor, and a Manual tab with the steps and an
mcp.jsonbox with the JSON to copy.
Connect Cursor
On the Gurusup MCP page, in the Connect Cursor dialog, click Add to Cursor on the Quick tab. Cursor opens and asks you to confirm. This installs the gurusup-brain server. Then sign in to Gurusup when Cursor asks. gurusup-brain then appears under Tools & MCP.
Open Tools & MCP
Open Settings with 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. Check the path Cursor shows: the project file or the global one, explained below the steps.
Paste the JSON
Paste this inside the file. If the Gurusup 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 and sign in
Save the file. Cursor detects the change, so no restart is needed. gurusup-brain shows as connected under Tools & MCP. If a sign-in page opens in your browser, sign in with the account you use for Gurusup. If you belong to more than one organization, choose it 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. Gurusup works from either.
| File | Gurusup is available |
|---|---|
.cursor/mcp.json in a project | In that project only |
~/.cursor/mcp.json in your home directory | In every project |
Save the instruction
Cursor keeps the instruction as a rule. Create .cursor/rules/gurusup-brain.mdc in your project, paste this and save:
---
description: Use Gurusup for questions about this company
alwaysApply: true
---
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.
Cursor's documentation says a plain .md file in .cursor/rules is ignored, so keep the .mdc extension. With alwaysApply: true the rule is 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 it can skip Gurusup on 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 Gurusup.
Check that it worked
Check the server
gurusup-brain shows as connected in the Tools & MCP list.
Check the tools
Ask Cursor: "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 Notion connected, for example: "Which Linear issues are open for the billing project, and what does our Notion spec say it should do?" Cursor 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 or off | Look for it under Tools & MCP and check its toggle is on |
Cursor does not connect after you edit mcp.json | Check that the JSON is valid and that other servers are still in the file |
| Cursor connects but does not use Gurusup | Check that the rule file ends in .mdc and has alwaysApply: true |
| You want to turn Gurusup off | Cursor's documentation says to 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 its mcp.json. |
For anything else, see MCP troubleshooting.