Join the beta

Learn

Connect Cursor to your company knowledge base

To connect Cursor to your company knowledge base, add Dienox in Cursor as an MCP server, with a personal token you make in Dienox. The AI that helps you write code can then read what the organisation knows: decisions, products, people and how the work runs. It is the same knowledge base your colleagues read from Claude or ChatGPT.

Updated

Before you start

  • Applies to. Cursor. Its documentation describes MCP as the way Cursor connects to external tools and data sources.
  • Plans. See Cursor's page.
  • How it connects. With a personal token that you make in Dienox. Windsurf and Gemini CLI connect the same way.
  • In Dienox. You need an account in your organisation, and an administrator invites you. Dienox is in beta, so your organisation joins the beta first.

Last checked: 1 October 2026

Menus change. Cursor's own documentation on MCP is leading for where a server is added in your version.

The steps

  1. In Dienox, open Settings, then AI tools, and choose Cursor.
  2. Make a token and copy it. You see it once. Choose read only if Cursor should look and change nothing.
  3. In Cursor, open Settings, then MCP, and add a new global MCP server.
  4. Paste the configuration that Dienox shows for Cursor, with your token in it.
  5. Save. Cursor connects by itself.

A token is like a password. Do not keep it in a document, and do not share it in a chat. When it expires, or when you lose it, you make a new one.

What you can ask now

Code is written for reasons that are rarely in the code. Now the AI that helps you write it can look those reasons up, and name the source.

  • "Why did we decide to bill per seat?" The decision, when it was made and by whom, with the reasons behind it.
  • "Who owns the integration with this supplier?" The person and the role, from what your organisation wrote down about who owns what.
  • "Name this feature the way we name things." Your products and how you sound, so the words in the code match the words in the rest of the organisation.

When something is settled while you work, Cursor can write it back, if your role and your token allow it. Then it is there for a colleague who asks in another tool.

For a whole team

With a token there is no step that one person takes for everyone. Each developer makes a token of their own and adds Dienox with the steps above.

That is deliberate. A token belongs to one person, so what Cursor writes appears under that person's name in the history. An administrator of your organisation invites people to Dienox, and can revoke a token at any time.

If it does not work

  • You did not copy the token. Dienox shows a token once. Make a new one.
  • It worked, and then it stopped. The token expired. You choose how long a token lasts when you make it. Make a new one.
  • Cursor reads but cannot write. The token is read only, or your role in the organisation is reader.
  • Every connection is refused. An administrator of your organisation has switched AI access off in Dienox, and can switch it on again.

The same knowledge in your other tools

Whatever you connect next reads the same knowledge base. What was settled in a chat here is there in the next tool, for you and for your colleagues.

Every tool side by side: connect your AI tools to your company knowledge. What the address you add does, and what it cannot do: the Dienox MCP server.

Questions people ask

Does Cursor sign in to Dienox, or use a token?

Cursor connects with a personal token. You make it in Dienox, under Settings and then AI tools, and paste the configuration Dienox shows into Cursor. The token belongs to you and to one organisation. You choose how long it lasts, and you can limit it to reading. You see it once, so copy it right away.

Can Cursor write to the knowledge base?

Yes, when your role and your token allow it. With a token that may write, Cursor can record what was decided, and the change appears under your name in the history, where it can be undone. With a read-only token, or as a reader, Cursor can look at the knowledge base and change nothing.

What does Cursor read from the knowledge base?

What the organisation knows: decisions and the reasons behind them, products and services, who owns what, and how the work runs. It reads within your role, in the one organisation the token belongs to. So the AI that helps you write code works from the same facts as your colleagues in Claude or ChatGPT.