Skip to main content
Microsoft 365 Copilot can query and analyze your data when connected to Nekt through the MCP Server. The connection is built in Microsoft Copilot Studio, which is where MCP servers are registered and attached to agents.
Unlike Claude or ChatGPT, Microsoft doesn’t let you plug an MCP server straight into the chat experience. You must create (or reuse) a Copilot Studio agent and attach the Nekt MCP Server to it as a tool. The agent then runs side by side with Microsoft 365 Copilot. This means you’ll be asked for agent details such as a name, description, and instructions — that’s expected, and the defaults are fine if you only want tool access.
Requires a paid Nekt plan (for MCP Server access) and a Microsoft Copilot Studio license in your Power Platform environment.

​
1. Activate your MCP Server

The connection is made by activating the MCP Server in your workspace. Check this guide for instructions.

​
2. Get your endpoint and token

Go to Integrations > MCP Server in the Nekt platform. You’ll need two values:
  • Endpoint — the MCP server URL displayed at the top of the page
  • Token — a bearer token created in the MCP Tokens section
If you don’t have a token yet, create one. You can scope it to specific tables or grant full access.
Tokens created manually can be scoped to specific tables for fine-grained access control. The agent can only reach the tables associated with the token you use.

​
3. Connect Copilot Studio to Nekt

1

Open or create an agent

Sign in to Copilot Studio and select the environment that will host the agent.Open an existing agent or select Create to build a new one. Give it a name and a description — for example, “Nekt Data Agent — answers questions about company data stored in Nekt.”
2

Start the MCP onboarding wizard

Open the agent’s Tools page, then select Add a tool > New tool > Model Context Protocol.
3

Fill in the server details

Complete the wizard fields:
Copilot Studio only supports the Streamable HTTP transport. The Nekt MCP Server uses HTTP transport, so it’s compatible.
4

Configure API key authentication

Select API key as the authentication type, then fill in the fields that appear:
Don’t put your token — or the word Bearer followed by the token — in any of these fields. They only describe where the credential goes. The token value itself is requested in the next step. Entering it here results in 401 Unauthorized errors when the agent calls Nekt.
Select Create.
5

Create the connection

The Add tool dialog appears. Select Create a new connection.Copilot Studio now prompts you for the credential, using the Parameter label you defined. Enter your Nekt token prefixed with Bearer and a space:
Replace MCP_TOKEN with the token from the MCP Tokens section in Nekt. Because the parameter name is Authorization, the whole value is sent as the header, so the Bearer prefix must be included here.Select Create, then Add to agent.
6

Verify the connection

Open the Connections section of the agent (or the tool’s detail panel) and confirm the Nekt connection shows as connected. If it isn’t, select Connect and complete the prompt.Once connected, Copilot Studio queries the server and lists the available Nekt tools under the connector. You can learn more about them here.
7

Enable the tool on the agent

Go to the agent’s Overview page and confirm the Nekt MCP server is listed and enabled under the agent’s tools. An agent won’t call a tool that’s connected but not enabled on it.
To reuse the same server on another agent, go to Tools > Add a tool and search for the name you gave it. Filter the connector types by Model Context Protocol — otherwise the server won’t appear in the results.

​
4. Test the agent

Use the Test your agent panel in Copilot Studio to check the connection before publishing. Ask a question about your data, for example:
The test panel shows which tools the agent calls. You should see the Nekt tools being invoked and their results feeding the answer.

​
5. Publish the agent

Changes made in Copilot Studio are not available to end users until the agent is published.
1

Publish

Select Publish in the agent. This applies to the initial setup and to every later change — including adding or reconfiguring the Nekt MCP server.
2

Make it available in Microsoft 365 Copilot

Go to the agent’s Channels section and add Microsoft 365 Copilot (and Microsoft Teams, if you want it there too). Depending on your tenant’s governance settings, an admin may need to approve the agent in the Microsoft 365 admin center before users can access it.
It can take up to an hour after publishing for the latest version of an agent to take effect, and users receive it the next time they message the agent. In channels with persistent conversations, send start over in the existing chat to force a new session with the published version.
We’d love to know what you’re building with Nekt! Share your projects with us through any of our communication channels.

​
Troubleshooting

This is almost always a misconfigured API key. Check that:
  • Parameter name is exactly Authorization and Parameter location is Header.
  • The token value was entered when creating the connection, not in the Parameter label field.
  • The connection value includes the Bearer prefix: Bearer MCP_TOKEN.
  • The token is still active in Integrations > MCP Server > MCP Tokens in Nekt.
To correct the credential, delete the connection and create a new one — editing the tool configuration alone does not update a stored connection.
Publish the agent again. Copilot Studio serves the last published version, so edits made in the authoring canvas — including newly added tools — don’t reach end users until you select Publish.If it’s already published, allow up to an hour for propagation and send start over in the chat to reset the session.
In the Add a tool dialog, filter the connector types by Model Context Protocol. Servers added through the MCP wizard are not returned by the default search filter.
Confirm the server is enabled on the agent’s Overview page, and that the Server description clearly states what the server does. The agent’s orchestrator uses that description to decide when to route a request to Nekt, so a vague description makes it less likely to be called.

​
Privacy & Security

Your data privacy is a core principle of the Nekt platform. When you connect Microsoft 365 Copilot to Nekt through the MCP Server, Copilot does not receive direct database credentials or unrestricted access to your infrastructure. Instead, it interacts with your data exclusively through the secure tools exposed by the Nekt MCP Server, which act as a controlled gateway to the Nekt API. These tools enforce the same authentication, authorization, and permission rules used throughout the Nekt platform. Access is scoped using tokens and user permissions, meaning the agent can only access the tables and actions explicitly allowed by the token stored in the connection. This architecture ensures that all queries, analysis, and data interactions remain governed, auditable, and restricted to your workspace permissions. Because the connection uses a shared API key rather than per-user OAuth, every user of the agent queries Nekt with the same token. Scope the token to the tables that everyone with access to the agent should be able to read. Access to MCP servers in Copilot Studio relies on Power Platform connectors, so any data loss prevention policy applied to Power Platform connectors also governs access to the Nekt MCP Server and its tools. When using Microsoft 365 Copilot, your interactions are subject to Microsoft’s privacy settings and policies. We recommend reviewing the official Microsoft privacy documentation to understand their data handling policies and selecting the configuration that best aligns with your organization’s security requirements.

​
Need help?

Contact our support team if you encounter issues during setup.