Roll out tools

Most AI clients have an admin policy, a managed file or admin console, that sets which MCP servers load. Use it to give every employee the Workforce MCP endpoint, https://wf-api.merge.dev/mcp, and where the client supports it, to block other servers.

Every employee gets the same config. Workforce decides which tools each person sees from their Groups, and each employee signs in once with SSO.

What each client supports

Client	Can install the endpoint	Can block other servers	Where the policy lives
Claude Code	Yes	Yes	`managed-mcp.json`
Codex	Yes	Yes	`/etc/codex/` or ChatGPT workspace policy
Gemini CLI	Yes	Yes	System `settings.json`
Cursor	No	Yes	Cursor admin dashboard
Windsurf	No	Yes	Windsurf Admin Portal
VS Code with Copilot	Yes	Partly	`mcp.json` plus device and GitHub policy
Claude (web and desktop)	No	No	Organization connector

Your MDM places the files below. Employees on clients that can’t install the endpoint follow Connect employee AI clients.

Claude Code

Deploy this file, owned by root. Claude Code then loads only this server.

managed-mcp.json

{
  "mcpServers": {
    "merge-workforce": {
      "type": "http",
      "url": "https://wf-api.merge.dev/mcp"
    }
  }
}

Platform	Path
macOS	`/Library/Application Support/ClaudeCode/managed-mcp.json`
Linux and WSL	`/etc/claude-code/managed-mcp.json`
Windows	`C:\Program Files\ClaudeCode\managed-mcp.json`

To check it, run claude mcp list on a test machine. Only the Workforce endpoint should appear. Employees sign in with claude mcp login merge-workforce.

managed-mcp.json also hides the organization’s claude.ai connectors in Claude Code. To keep them, set "allowAllClaudeAiMcps": true in managed settings.

Codex

Install the endpoint with managed_config.toml:

managed_config.toml

[mcp_servers.merge_workforce]
url = "https://wf-api.merge.dev/mcp"
auth = "oauth"

Make it the only allowed server with requirements.toml:

requirements.toml

[mcp_servers.merge_workforce]
identity = { url = "https://wf-api.merge.dev/mcp" }

Both files go in /etc/codex/ on macOS and Linux, and ~/.codex/ on Windows. You can also apply the same policy from a ChatGPT enterprise workspace.

Gemini CLI

Add the endpoint under mcpServers in the root-owned system settings.json, and set mcp.allowed to block other servers.

Cursor, Windsurf, and VS Code

These clients can block other servers but can’t install the endpoint for the employee:

Cursor: allowlist only the Workforce endpoint URL in the admin dashboard
Windsurf: allowlist only the Workforce endpoint in the Admin Portal
VS Code with Copilot: install the endpoint with mcp.json, then set the ChatMCP=registry device policy. Use ChatMCP=none to block all MCP servers

Claude (web and desktop)

An Owner adds Workforce once under Organization settings → Connectors. Each employee then connects it themselves.

Limits

These policies run on the employee’s machine, so someone with local admin rights can bypass them. They still can’t reach your tools without signing in to Workforce.