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.

Filter chips let you scope the list by Transport (Local or Remote) and by Config source, with each chip showing how many servers match.

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: Local for a process started on the device, or Remote for a server reached over the network
• 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. Claude Code plugin and Codex plugin mean the server is supplied by an installed agent plugin, and Discovered means the configuration file was found on disk rather than read from a known tool's configuration.

  • Plugin: for a server supplied by an agent plugin, the plugin it comes from. Select it to open the plugin on the Agent Plugins page.
• 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

  Agent plugin marketplaces are catalogs, and each catalog entry can ship a template .mcp.json for a plugin that is not installed. Those templates are not reported as MCP servers. A plugin's own MCP servers are reported only when the plugin is installed, and are attributed to that plugin. Requires agent v1.17.0 or later.