Connect Nicoka in Microsoft Copilot
The Nicoka MCP connects Microsoft Copilot to your Nicoka workspace: candidates, jobs, contacts, opportunities, invoices. You ask your questions in Copilot, the answer appears in the conversation, with your rights and your data. When you ask for it, Copilot also creates items in Nicoka, such as a note or a task.
Two paths, depending on your Copilot
- Copilot Studio: you add the Nicoka MCP server as a tool of an agent. This is the most direct path, with no client ID or secret to create beforehand. Start with this one.
- Microsoft 365 Copilot: you declare Nicoka as a connector for the whole organization, from the Microsoft 365 admin center. Reserved for an administrator, and it requires an OAuth registration first, plus some preparation on the Nicoka side.
Before you start
- Your MCP server address:
https://YOUR-INSTANCE.nicoka.com/api/mcp. Replace YOUR-INSTANCE with the subdomain of your Nicoka workspace, the one in your browser's address bar. If in doubt, ask Nicoka support. - On the Nicoka side: your profile must allow you to connect an application. If the connection is refused, ask your company's Nicoka administrator.
- On the Microsoft side: adding a tool or a connector depends on your license and on your organization's rules. If in doubt, check with your Microsoft 365 administrator.
Path 1. Add Nicoka to a Copilot Studio agent
- Open your agent in Copilot Studio, then the Tools page.
- Select Add a tool, then New tool.
- In the Create new section, select Model Context Protocol: the MCP onboarding wizard opens.
- Fill in the three required fields:
- Server name: Nicoka;
- Server description: for example "Nicoka data: candidates, jobs, contacts, opportunities, invoices". The agent uses it to decide when to call Nicoka;
- Server URL:
https://YOUR-INSTANCE.nicoka.com/api/mcp.
- As the authentication type, select OAuth 2.0, then the Dynamic discovery type. Nicoka publishes its authorization endpoints and registers the agent by itself: you have no client ID or secret to enter.
- Select Create, then Next: the Add tool dialog appears.
- Select Create a new connection. Copilot redirects you to Nicoka: sign in with your usual account if you are not already signed in, then, on the Authorize access screen, check the permissions shown and select Authorize.
- Back in Copilot Studio, select Add to agent.
Test it in the agent's conversation pane, for example: "List my 5 latest opportunities in Nicoka". Copilot never has access to your Nicoka password, and it acts with your rights: it only sees what you see in Nicoka.
Path 2. Declare Nicoka as a Microsoft 365 Copilot connector
This path is reserved for an administrator with the Global Administrator or AI Administrator role. It has two stages: the OAuth registration in the Teams Developer Portal, then the creation of the connector.
This path requires preparation on our side: contact Nicoka support before you start. Microsoft's redirect address, https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect, is not allowed by default on your workspace; support adds it and gives you the OAuth client ID and client secret. Without this step, the connection is refused.
a. Register the OAuth connection
- Sign in to the Teams Developer Portal.
- Open Tools, then OAuth Client Registration, and select New OAuth connection.
- Fill in the connection:
- Name: Nicoka;
- Client ID and client secret: the ones provided by Nicoka;
- Authorization endpoint:
https://YOUR-INSTANCE.nicoka.com/api/oauth/authorize; - Token endpoint and refresh endpoint:
https://YOUR-INSTANCE.nicoka.com/api/oauth/token; - Scopes:
mcp:read mcp:write.
- Turn on PKCE, which Nicoka supports, then save. Note the OAuth client registration ID that appears: it is required in the next stage.
b. Create the connector
- In the Microsoft 365 admin center, open Copilot, then Connectors.
- On the Gallery tab, in the Created by your org section, select Add on the Create a new connector tile.
- On the Custom connector page, under Connect to MCP server, select Add.
- Fill in the display name (Nicoka), a description of the data it gives access to, and the base URL:
https://YOUR-INSTANCE.nicoka.com/api/mcp. - Enter the OAuth registration ID from the Teams Developer Portal, then select Save.
The connector appears in Your connections. Roll it out to a few users first with the staged rollout, then to the whole organization. Allow up to ten minutes for the change to propagate. Each user then connects with their own Nicoka account, from Settings then Sources in Copilot.
If something goes wrong
- The server cannot be created in Copilot Studio: check that the address ends with
/api/mcp, and that you selected OAuth 2.0 then Dynamic discovery. - Nicoka refuses access: your Nicoka profile does not allow you to connect an application. Contact your company's Nicoka administrator.
- Nicoka refuses the redirect address: Microsoft's address has not been allowed on your workspace yet. That is the preliminary step of path 2: contact Nicoka support.
- Copilot does not use Nicoka: check that the tool is added to the agent, then name Nicoka in your request: "In Nicoka, list my 5 latest opportunities".
- A user cannot see the Microsoft 365 connector: check that they are included in the staged rollout and in user access, then ask them to start a new conversation.
- Your workspace filters access by IP address: allow the Microsoft 365 Copilot egress addresses, listed in the Microsoft documentation.
- The authorization has expired or new tools do not appear: disconnect then reconnect Nicoka, as explained in Refresh your AI connection with Nicoka (MCP).
What the assistant can do, module by module, is detailed in What your AI assistant can do in Nicoka (MCP). Need help? Contact Nicoka support.