Connect Cursor to your company knowledge

Cursor knows your codebase better than most of your colleagues do. It has read every file, it follows your patterns, and it still calls your flagship feature by its database column name. The missing piece is company knowledge: what things are called in front of customers, which terms mean what, which claims you are allowed to make. That knowledge lives in people's heads and in a document nobody opens, so it never reaches the editor.

Company Brain holds your company's approved facts, product names, terminology and rules, and delivers them to Cursor through MCP. You add one entry to Cursor's MCP configuration, restart the app, and every Agent session can pull reviewed company knowledge before it writes. Setup takes about five minutes, and the same connection works for everyone on the team.

A dated honesty note before we start: these steps match Cursor as of October 2026. Cursor ships fast and its settings screens move. If a menu has drifted by the time you read this, the shape of the process holds, and the connection page inside Company Brain stays current. Picture a developer who keeps a product glossary in a scratch file and pastes it at the top of every session. That scratch file is the problem this connection removes.

Before you start

You need a Company Brain account with some facts already written in. Connecting an empty source produces a very polite nothing, so if the facts are missing, write the naming and terminology ones first. For a code editor, the facts that matter most are vocabulary: what products and features are called externally, which domain terms carry precise meanings, and which words are off limits in user facing text.

You also need Cursor installed, which I will assume, since you searched for how to connect it. If MCP itself is new to you, what MCP is, explained without code covers the protocol in plain language before you touch any configuration.

Step one: get your connection URL

Sign in to Company Brain and open the connection page. You will find one URL for your company. That URL contains your connection key, and the key is the credential. There is no separate login step in Cursor. Whoever holds the URL holds the access, so treat the whole URL like a password: keep it out of shared repos, out of screenshots, and out of chat messages you would regret.

Copy it. That is all this step is.

Step two: add the Company Brain entry to Cursor's config

Cursor reads its MCP servers from a JSON file. The global file lives at ~/.cursor/mcp.json and applies to every project. A per project file at .cursor/mcp.json inside a repo applies to that repo only. For company knowledge, the global file is usually the right home, since your product names do not change between repositories. You can also reach the same configuration by searching for MCP in Cursor's settings.

Open the file, or create it if it does not exist, and add the Company Brain entry:

{
  "mcpServers": {
    "companybrain": {
      "url": "YOUR_CONNECTION_URL",
      "type": "streamableHttp"
    }
  }
}

Replace the placeholder with the real address from your connection page. The connection page in Company Brain hands you this snippet ready-made, with your company's real address already filled in, so the easiest path is to paste that one. The entry name is yours to choose. If the file already has other servers under mcpServers, add this entry alongside them and keep the rest of the object as it is. Mind the type field: the value must be exactly streamableHttp.

Step three: restart Cursor properly

Fully quit Cursor and open it again. MCP servers load at startup, so reloading the window does not pick up the new entry. It is an easy step to skip, and the connection looks dead without it, even when the config is perfectly fine. Quit the application, all the way, then start it fresh.

Step four: confirm the tools are there

Open a new Composer and make sure it is in Agent mode. MCP tools are only offered in Agent mode, so a normal chat will never show them no matter how correct your config is.

Two quick checks confirm everything loaded. Type @ in the Composer and look for the Company Brain tools in the list. Then open Settings, find the MCP section, and look for the green dot next to the server entry. Green dot plus listed tools means you are connected.

Test it with real work

A connection test with "what do you know about my company" tells you very little. Test with the work you would otherwise have briefed by hand.

Ask the Agent to write a changelog entry for a feature whose internal name differs from its customer facing name. Ask it to draft the error message copy for a flow your rules constrain. Watch for the external name spelled right and the forbidden claims left out. When something comes back wrong, that is a finding too: it usually means a fact is missing or vague, and now you know exactly which one to add.

The before and after is easy to feel. That scratch-file glossary is the first thing that stops getting pasted. The facts follow you into every repo, and when the curator renames something, your next session picks it up without you doing anything.

If it does not show up

Four checks resolve nearly every stuck setup.

First, the restart. Fully quit Cursor and reopen it. A window reload looks like a restart and does nothing for MCP servers.

Second, the mode. Open a new Composer in Agent mode and check that the MCP tools are switched on for it. Outside Agent mode the tools simply never appear.

Third, the type field. The value must read exactly streamableHttp. A value of http points Cursor at a different transport.

Fourth, the green dot. Open Settings, go to the MCP section, and look for the green dot next to the Company Brain entry. If it is missing, recheck the address you pasted against the connection page.

One address, whole team

Every teammate repeats steps two and three with the same URL, a few minutes each. From then on, everyone's Cursor draws from the same reviewed facts, and so does everyone's ChatGPT and Claude, because the whole company shares one endpoint across every tool. Your colleagues who live in a browser can follow the guide to connect ChatGPT to the same company knowledge, and the landing page covers why Cursor and Company Brain fit together if someone on the team wants the short version before setting it up.

The configuration outlives the setup. Facts change, repos come and go, people join, and the entry in mcp.json just sits there doing its job. Five minutes, one JSON block, and the glossary scratch file can finally be deleted.