Roll Out Dtwo in Cursor
Roll out your Dtwo gateway to everyone in your organization in Cursor.
On this page
Overview
This guide walks you through rolling out Dtwo to your whole organization in Cursor and turning off direct connections to MCP servers. If you only want to set it up for yourself, see Connect Cursor for yourself.
Rolling out Dtwo to your organization needs a Cursor Teams or Enterprise plan and admin access to your team in the Cursor dashboard.
Roll out Dtwo to your organization in Cursor
Select how your gateway signs people in.
Step 1: Add the gateway for everyone in your organization
Cursor can’t push an MCP server to people on its own, but it can push a plugin, and a plugin can contain your gateway. You’ll put the gateway in a plugin, add it to your team marketplace, and make it required.
-
Create a plugin that contains your gateway. Follow Cursor’s plugins guide and put this in the plugin’s
mcp.json:{ "mcpServers": { "<GatewayName>": { "url": "<GatewayURL>", "auth": { "CLIENT_ID": "<ClientId>" } } } }Replace the placeholders:
<GatewayName>: your gateway’s name.<GatewayURL>: your gateway’s MCP URL. Copy it from your gateway’s Overview tab in the Dtwo UI. It must start withhttps://.<ClientId>: Cursor’s client ID. Go to your gateway in the Dtwo UI, open Configuration → Authentication, and copy the client ID.
-
Add it to your team marketplace in the Cursor dashboard under Plugins & MCPs. See Add a team marketplace.
-
Set Plugin Installation to Required, so it’s installed for everyone and can’t be removed. See Plugin installation modes.
Each person signs in once with their Dtwo account, from Customize → MCPs.
Step 2: Turn off direct connections to MCP servers
For the Enterprise plan. Cursor’s MCP allowlist blocks every server that doesn’t match an entry on it.
- In the Cursor dashboard, open your team settings and go to MCP Configuration.
- Add one URL entry with your gateway’s MCP URL, and leave its tools field empty so every tool is allowed. Copy the URL from your gateway’s Overview tab in the Dtwo UI. It must start with
https://. - Save the allowlist.
The allowlist only applies when people are signed in to your team.
Step 3: Check the rollout
- Open Customize → MCPs and confirm your gateway is switched on with its tools listed.
- In a chat, ask which tools it has through your gateway. It should list the tools from the MCP servers behind your gateway.
- If you turned off other servers, add any other server to your
mcp.json. Cursor blocks it from running.
Step 1: Get Cursor's client ID from Microsoft Entra ID
If you’ve already registered Cursor as an app in Microsoft Entra ID, go to App registrations, open the Cursor app, and copy the Application (client) ID from its Overview page. This is your <ClientId>.
If you haven’t registered Cursor in Microsoft Entra ID yet, follow Register Cursor in Microsoft Entra ID, then come back here.
Step 2: Add the gateway for everyone in your organization
Cursor can’t push an MCP server to people on its own, but it can push a plugin, and a plugin can contain your gateway. You’ll put the gateway in a plugin, add it to your team marketplace, and make it required.
-
Create a plugin that contains your gateway. Follow Cursor’s plugins guide and put this in the plugin’s
mcp.json:{ "mcpServers": { "<GatewayName>": { "url": "<GatewayURL>", "auth": { "CLIENT_ID": "<ClientId>" } } } }Replace the placeholders:
<GatewayName>: your gateway’s name.<GatewayURL>: your gateway’s MCP URL. Copy it from your gateway’s Overview tab in the Dtwo UI. It must start withhttps://.<ClientId>: the client ID from Step 1.
-
Add it to your team marketplace in the Cursor dashboard under Plugins & MCPs. See Add a team marketplace.
-
Set Plugin Installation to Required, so it’s installed for everyone and can’t be removed. See Plugin installation modes.
Each person signs in once, from Customize → MCPs.
Step 3: Turn off direct connections to MCP servers
For the Enterprise plan. Cursor’s MCP allowlist blocks every server that doesn’t match an entry on it.
- In the Cursor dashboard, open your team settings and go to MCP Configuration.
- Add one URL entry with your gateway’s MCP URL, and leave its tools field empty so every tool is allowed. Copy the URL from your gateway’s Overview tab in the Dtwo UI. It must start with
https://. - Save the allowlist.
The allowlist only applies when people are signed in to your team.
Step 4: Check the rollout
- Open Customize → MCPs and confirm your gateway is switched on with its tools listed.
- In a chat, ask which tools it has through your gateway. It should list the tools from the MCP servers behind your gateway.
- If you turned off other servers, add any other server to your
mcp.json. Cursor blocks it from running.
Step 1: Get Cursor's client ID from Okta
If you’ve already registered Cursor as an app in Okta, go to Applications and Resources → Applications, open the Cursor app integration, and copy the Client ID from its General tab. This is your <ClientId>.
If you haven’t registered Cursor in Okta yet, follow Register Cursor in Okta, then come back here.
Step 2: Add the gateway for everyone in your organization
Cursor can’t push an MCP server to people on its own, but it can push a plugin, and a plugin can contain your gateway. You’ll put the gateway in a plugin, add it to your team marketplace, and make it required.
-
Create a plugin that contains your gateway. Follow Cursor’s plugins guide and put this in the plugin’s
mcp.json:{ "mcpServers": { "<GatewayName>": { "url": "<GatewayURL>", "auth": { "CLIENT_ID": "<ClientId>" } } } }Replace the placeholders:
<GatewayName>: your gateway’s name.<GatewayURL>: your gateway’s MCP URL. Copy it from your gateway’s Overview tab in the Dtwo UI. It must start withhttps://.<ClientId>: the client ID from Step 1.
-
Add it to your team marketplace in the Cursor dashboard under Plugins & MCPs. See Add a team marketplace.
-
Set Plugin Installation to Required, so it’s installed for everyone and can’t be removed. See Plugin installation modes.
Each person signs in once, from Customize → MCPs.
Step 3: Turn off direct connections to MCP servers
For the Enterprise plan. Cursor’s MCP allowlist blocks every server that doesn’t match an entry on it.
- In the Cursor dashboard, open your team settings and go to MCP Configuration.
- Add one URL entry with your gateway’s MCP URL, and leave its tools field empty so every tool is allowed. Copy the URL from your gateway’s Overview tab in the Dtwo UI. It must start with
https://. - Save the allowlist.
The allowlist only applies when people are signed in to your team.
Step 4: Check the rollout
- Open Customize → MCPs and confirm your gateway is switched on with its tools listed.
- In a chat, ask which tools it has through your gateway. It should list the tools from the MCP servers behind your gateway.
- If you turned off other servers, add any other server to your
mcp.json. Cursor blocks it from running.