Skip to main content
Glama
danielrosehill

Daniel Rosehill's MCP Installer

list_installed

Check which MCP servers are installed in specific clients or across all supported platforms to manage configurations and installations.

Instructions

Show what MCPs are already installed in a specific client or all clients.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientNoClient to checkall

Implementation Reference

  • Main handler logic for the 'list_installed' tool. Handles requests for a specific client or all clients by calling helper functions to retrieve client info and installed MCPs, then formats and returns JSON response.
    case 'list_installed': {
      const clientArg = (args?.client as string) || 'all';
    
      if (clientArg === 'all') {
        const clientInfo = getAllClientInfo();
        const result: Record<string, { path: string; exists: boolean; mcps: string[] }> = {};
    
        for (const [client, info] of Object.entries(clientInfo)) {
          const installed = getInstalledMcps(client as ClientType);
          result[client] = {
            path: info.path,
            exists: info.exists,
            mcps: Object.keys(installed)
          };
        }
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }]
        };
      } else {
        const installed = getInstalledMcps(clientArg as ClientType);
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              client: clientArg,
              count: Object.keys(installed).length,
              mcps: Object.keys(installed)
            }, null, 2)
          }]
        };
      }
    }
  • Tool schema definition including name, description, and inputSchema for the 'list_installed' tool, which specifies the 'client' parameter.
    {
      name: 'list_installed',
      description: 'Show what MCPs are already installed in a specific client or all clients.',
      inputSchema: {
        type: 'object',
        properties: {
          client: {
            type: 'string',
            enum: ['claude-code', 'cursor', 'vscode', 'all'],
            description: 'Client to check',
            default: 'all'
          }
        }
      }
    },
  • Helper function getAllClientInfo() that returns configuration info for all supported clients, used when listing installed MCPs for all clients.
    export function getAllClientInfo(): Record<ClientType, ClientInfo> {
      const result: Record<ClientType, ClientInfo> = {} as Record<ClientType, ClientInfo>;
      for (const client of Object.keys(CLIENT_CONFIGS) as ClientType[]) {
        result[client] = getClientInfo(client);
      }
      return result;
    }
  • Helper function getInstalledMcps(client) that reads the client's settings and returns the map of installed MCP servers.
    export function getInstalledMcps(client: ClientType): Record<string, McpServerConfig> {
      const settings = readClientSettings(client);
      return settings.mcpServers || {};
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the tool shows installed MCPs but doesn't disclose behavioral traits such as whether it's read-only, what the output format is (e.g., list, JSON), if there are rate limits, or any authentication needs. This leaves significant gaps in understanding how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the purpose ('Show what MCPs are already installed') and specifies the scope. There is no wasted text, making it appropriately sized and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list of MCP names, details), behavioral aspects, or error handling. For a tool with one parameter but missing structured output info, more context is needed to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'client' fully documented in the schema (including enum values and default). The description adds minimal value by mentioning 'specific client or all clients', which aligns with the schema but doesn't provide additional semantics beyond what's already structured.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Show' and the resource 'MCPs already installed', specifying the scope as 'in a specific client or all clients'. It distinguishes from siblings like 'list_mcps' (which likely lists available MCPs) by focusing on installed ones, though it doesn't explicitly name the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing to check installed MCPs, with the parameter 'client' allowing filtering. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_info' (which might provide client details) or 'list_mcps' (which might list available MCPs), leaving usage context somewhat inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielrosehill/My-MCP-Installer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server