One connector, every tool
A team does not use one AI tool. Sales works in one, finance in another, and the developers in a third. Each of those tools can reach something outside itself through a connector. Add the same one in each, and every tool reads the same knowledge base.
A connector to one system gives that one tool that one system. A knowledge base gives every tool what the company knows.
The home page shows it from the first connection on: connect once, and every chat knows the company. Nobody has to change tools. Nothing has to be pasted in again. Dienox calls the result universal AI context.
The address you add is the same for everyone:
https://dienox.com/mcp
Which organisation a tool reads is chosen when you sign in.
Connectors, and MCP underneath
Connector is the word most people use. Claude has connectors, and one you add yourself is a custom connector. People say ChatGPT connectors as well, and ChatGPT's own word for one you add yourself is a custom app.
MCP is the developers' word for what sits underneath. MCP, the Model Context Protocol, is the open standard AI tools use to connect to data and systems. Anthropic introduced it on 25 November 2024, and other AI providers have adopted it since.
You do not need to know more than that to connect. The standard is published at modelcontextprotocol.io, and the Dienox MCP server says what ours does, in plain words.
Pick your tool
Each page gives the steps for one tool, who adds it for a team, and what to do when it does not work.
- Claude As a custom connector, on the web and in the desktop app.
- ChatGPT As a custom app, published once for a whole workspace.
- Microsoft Copilot Through Copilot Studio, as a tool on an agent.
- Cursor As an MCP server, with a personal token.
Claude Code, VS Code, Windsurf, Gemini CLI and any other MCP client connect as well. Once your organisation is on Dienox, it gives you the steps for each of them when you are signed in.
Where the connector goes, per tool
This is what each vendor says about its own tool, as we read it on 1 October 2026. Plans and menus change, so the vendor's own guide is leading. It is linked in the last column.
| Tool | Where the connector goes | Who adds it for a team | Which plans | The vendor's guide |
|---|---|---|---|---|
| Claude | Customize, then Connectors, as a custom connector | An owner, on Team and Enterprise. Each member then connects. | Free, Pro, Max, Team and Enterprise. Free is limited to one custom connector. | Claude Help Center: custom connectors |
| ChatGPT | Workspace settings, then Apps, as a custom app | An admin or owner creates the app and publishes it. Each member then adds it. | Business, Enterprise and Edu, in beta, on the web. | OpenAI Help Center: developer mode and MCP apps |
| Microsoft Copilot | Copilot Studio, as a tool on an agent | Someone with rights in your Copilot Studio environment. | See Microsoft's page. | Microsoft Learn: connect your agent to an existing MCP server |
| Cursor | Cursor's settings for MCP, as an MCP server | Each person, with a token of their own. | See Cursor's page. | Cursor documentation: MCP |
A word on Copilot. Dienox works in Microsoft Copilot through Copilot Studio. Microsoft 365 Copilot additionally needs an agent that your IT team publishes.
What the AI can read once it is connected
A connected tool reaches one thing through Dienox: the knowledge base of the organisation you picked when you signed in.
- One organisation. A connection belongs to one organisation. It cannot see or reach another, whoever asks.
- Your role. Administrator, editor or reader. The tool works within the role you have, never a wider one.
- When a question needs it. The tool reads the knowledge base when a question needs it. Nothing has to be pasted in first.
- With the source. The answer comes with the source under it, so you can check it.
What a tool reaches through its other connectors is decided by those connectors, not by Dienox.
Who sets it up in a team
Two things happen, by two kinds of people.
- Once, for everyone. Where an AI tool has a team plan, someone with the right role adds Dienox for the whole team. In Claude that is an owner. In ChatGPT it is an admin or owner of the workspace. In Copilot Studio it is someone with rights in that environment.
- Once per person. Each colleague then connects with their own Dienox account. So the AI works within that person's role, and what it writes carries their name.
Each colleague needs an account in your organisation on Dienox first, and an administrator invites them. On a personal plan there is no first step: you add Dienox yourself.
Can a connected tool change things?
Yes, within limits. A tool that works for an administrator or an editor can write back what was decided. Every change is kept in the history, with who made it and when, and can be undone. A reader's tool only reads.
Actions on your other systems are a separate matter. Each one is read, write or irreversible, and switched on or off per agent: AI agents that cannot do what you did not allow.
Questions people ask
How do I connect Claude to my company knowledge base?
Add Dienox in Claude as a custom connector, with the address https://dienox.com/mcp. Click Connect, sign in to Dienox and pick your organisation. On a Team or Enterprise plan an owner adds the connector once, and each member then connects their own account. From then on Claude reads the knowledge base when a question needs it.
How do I connect ChatGPT to my company knowledge base?
In a ChatGPT Business, Enterprise or Edu workspace, an admin or owner adds Dienox once as a custom app and publishes it. Each member then finds it under Apps in ChatGPT, adds it and signs in to Dienox with their own account. That is how OpenAI describes it at the time of writing, and its own page is leading.
What data can Claude access through a connector?
Through the Dienox connector, Claude can reach one thing: the knowledge base of the organisation you picked when you signed in. It works within your role there, and it cannot see another organisation. The answer comes with its source, so you can check it. What Claude reaches through other connectors is decided by those connectors.
Do we have to install anything?
No. Dienox is added inside the AI tool you already use: as a custom connector in Claude, a custom app in ChatGPT, a tool in Copilot Studio or an MCP server in Cursor. There is no program to download and no extension to add. It takes about a minute per person.
Does every colleague have to connect separately?
Yes, and that is deliberate. Each person connects with their own Dienox account, so the AI works within that person's role and what it writes carries their name. Where an AI tool has a team plan, an owner or admin adds Dienox once for everyone. After that, each member only has to connect.
Can Claude and ChatGPT read the same knowledge base?
Yes. Both connect to the same knowledge base in Dienox, so both start from the same facts. What was decided in a chat in Claude is there when a colleague asks in ChatGPT. By themselves the two share nothing: each keeps its own memory and its own projects. One source outside both is what joins them.
Claude connectors or MCP: what is the difference?
A connector is what you add in Claude to reach something outside it. MCP, the Model Context Protocol, is the open standard a custom connector speaks. They are the two ends of one connection: the connector sits in Claude, and an MCP server, such as the one Dienox offers, sits at the address the connector points to.
Can a connected AI tool change our knowledge?
Yes, when the person it works for may. The AI tool of an administrator or an editor can write back what was decided, and a reader's tool can only read. Every change is recorded under the person's name, kept in the history and can be undone. Actions on your other systems have limits of their own.