Skip to main content

MCP Server

The N3O MCP server is how you connect an AI assistant of your choosing to N3O Cloud. Someone on your team asks in plain language, and the assistant answers from your own data or carries the work out in N3O Cloud. Which of the two it can do depends on the tools N3O has built, and more arrive over time.

MCP stands for Model Context Protocol, the standard an AI assistant uses to reach data and work held in another system. N3O's server is what you point an assistant at to reach your own subscription.

Availability​

The MCP server is not available until it is turned on for your subscription. Ask your N3O contact to enable it, and to confirm that the assistant you want to use is supported.

Who can use it​

Each person signs in with their own N3O Cloud account the first time they use the assistant, and it acts as them from then on. There is nothing to configure per person, but each person needs an account in your subscription before they can use it. Beyond that there is no separate permission to grant, and one person reaches the same data as any other. What an assistant reaches is the data your subscription holds, personal data included, and whatever it does in N3O Cloud is done in the name of the person signed in. Deciding who may use the connection is deciding who sees that data and what may be done in their name.

A person can hold more than one N3O Cloud account: one they reach through your organisation's Microsoft account, and one they reach with an email address and password. These are separate accounts, and only the one that belongs to your subscription works, so that is the one to sign in with. Signing in to an assistant can complete without asking, as whoever is already signed in to N3O Cloud in that browser.

Who can open the assistant in the first place is decided on the assistant's own side, by whoever set it up for your team.

Your address​

Each subscription has its own address, and it is what you give an assistant when you connect it:

https://eu1.n3o.cloud/api/mcp/{subscription}

The last part is your subscription code. Your N3O contact gives you the full address when the server is turned on, and can confirm the code at any time.

What an assistant can do​

The server offers the assistant a set of tools, and the assistant chooses which of them to use; you only ask. They reach the parts of N3O Cloud your team already works in, and the set grows as N3O builds it out. Ask your N3O contact what is available to your subscription today.

Some tools read and some change a record, and the server marks which is which. Whether an assistant asks you before it runs a tool, and how often, is the assistant's to decide, and each assistant's page below says how it asks. The server never acts on its own, and a tool runs only because someone asked for something that needed it.

Connecting an assistant​

Each assistant is connected in its own way, and each needs your subscription's address.

  • ChatGPT covers turning on developer mode and creating an app for the server.
  • Claude covers adding the server as a custom connector, for one person or for your whole organisation.
  • Microsoft 365 Copilot covers building an agent in Copilot Studio and publishing it to your team in Teams and Microsoft 365 Copilot chat.

Further reading​