MCP Servers

The MCP Servers page provides an organization-wide view of all Model Context Protocol (MCP) servers configured across developer machines.

MCP servers extend AI agents by enabling them to interact with external systems, APIs, and local tools. This page helps you understand where those integrations exist and how widely they are deployed.

The MCP server table shows the following columns:

• Server: the MCP server name (for example, npx~server-brave-search, npx~server-filesystem)

• Transport: how the server is invoked (for example, local)

• Config Sources: the AI tools that have this server registered in their configuration (for example, cursor, antigravity, windsurf). Multiple sources may be shown per row when the same server is configured by more than one tool.

• Devices: the number of devices where the server is configured

Expanding a Server

Each MCP server row can be expanded to view device-level details.

When expanded, you can see:

• Device ID – The unique identifier of the developer machine

• Configuration or execution details where applicable

This allows you to:

• Identify which machines have a specific MCP server configured

• Detect duplicate or redundant configurations

• Investigate potentially risky integrations

• Validate compliance with approved MCP server policies