Manage MCP servers
See which MCP servers your teams use, and push approved servers to their devices from one place.
The MCP Servers page shows which MCP servers people use and which ones are installed on their devices. Admins can also add managed servers, which the Tokenize desktop app installs on the selected devices.
Who can do this: Admins add, edit, and remove managed servers. People with usage access see the whole organization. Everyone else sees only their own devices and usage.
The tabs
| Tab | What it shows |
|---|---|
| Recently Used | Servers used in the selected date range, with Users, Tool calls, % failed, and Last seen. |
| On Devices | Servers found on devices, with Team, Surfaces, Users, Devices, and Last seen. |
| Managed | Servers your organization pushes to devices. |
If you don't have usage access, the tabs cover only you. Recently Used shows "What you used recently." On Devices lists the servers on your own devices. In page search, this tab is called My Devices. Managed is read-only.
With usage access, you can filter the whole page by team with the picker at the top right.
Add a managed server
- Go to MCP Servers and open the Managed tab.
- Click Add Server.
- Enter a Name. To pick from a list, click the arrow (Browse known servers). The list includes servers already running on your devices and common public servers. Picking one fills in the rest of the form. Names use letters, numbers, hyphens, and underscores.
- Choose a Connection type:
- Hosted server: enter a Server URL (HTTPS only). Add Headers if the server needs them.
- Local command: enter the Local command and any Command arguments (Optional), one per line. Add Environment variables if the server needs them.
- Under Send to, pick one or more teams. Leave it empty to send to every device.
- Click Add Server.
Header and environment variable values go to every targeted device. Don't use personal credentials. Use OAuth when the server supports it.
Managed servers reach the selected devices within 15 minutes. They install in Claude Code, Cowork, Codex, and Cursor wherever those apps are present. People may need to restart their apps before the server shows up.
To change a server, click its edit button in the Managed table, then Save changes. You can't rename a server. To rename one, remove it and add it again.
Remove a managed server
Click the remove button on the server's row, then confirm Remove. This removes the server from every device in your organization on their next sync.
Check delivery
Admins see delivery status at the top of the Managed tab. Each device that has checked in is counted in one bucket:
| Status | What it means | What to do |
|---|---|---|
| Up to date | The device has the latest managed server list. | Nothing. |
| Pending | The device hasn't picked up the latest list yet. | Wait up to 15 minutes. If a device stays pending, check that the desktop app is running and up to date. See Troubleshoot the desktop app. |
| Blocked | The device tried to apply the list but couldn't write to at least one app. | Click Show devices to see which app failed. |
| Stale | The device hasn't reported in a long time. | Check whether the device is still in use. See Manage devices. |
Click Show devices for a per-device view. It shows one column per app (Claude Code, Cowork, Cursor, Codex):
- Applied or Not installed: fine. Not installed means that app isn't on the device.
- Unreadable config: the app's config file couldn't be parsed. Fix or remove the broken file on that device.
- Changed mid-write: the file changed while Tokenize was writing. It usually clears on the next sync.
- Read failed or Write failed: Tokenize couldn't read or write the file. Check file permissions on that device.
The Status column in the Managed table is separate. Active means the server has been seen on at least one device. Pending means no device has reported it yet. Use the delivery status above the table to see how many devices are up to date.
New servers that show up on devices also trigger a New MCP server alert. See Alerts.