Skip to main content
Glama

get_config

Read-only

Retrieve the complete Desktop Commander MCP server configuration as JSON, including security settings, access controls, system details, and client information.

Instructions

                    Get the complete server configuration as JSON. Config includes fields for:
                    - blockedCommands (array of blocked shell commands)
                    - defaultShell (shell to use for commands)
                    - allowedDirectories (paths the server can access)
                    - fileReadLineLimit (max lines for read_file, default 1000)
                    - fileWriteLineLimit (max lines per write_file call, default 50)
                    - telemetryEnabled (boolean for telemetry opt-in/out)
                    - currentClient (information about the currently connected MCP client)
                    - clientHistory (history of all clients that have connected)
                    - version (version of the DesktopCommander)
                    - systemInfo (operating system and environment details)
                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'get_config' tool. It retrieves the server configuration, enriches it with system information, memory usage, current client details, and feature flags, then returns it as formatted JSON text content.
    export async function getConfig() {
      console.error('getConfig called');
      try {
        const config = await configManager.getConfig();
        
        // Add system information and current client to the config response
        const systemInfo = getSystemInfo();
        
        // Get memory usage
        const memoryUsage = process.memoryUsage();
        const memory = {
          rss: `${(memoryUsage.rss / 1024 / 1024).toFixed(2)} MB`,
          heapTotal: `${(memoryUsage.heapTotal / 1024 / 1024).toFixed(2)} MB`,
          heapUsed: `${(memoryUsage.heapUsed / 1024 / 1024).toFixed(2)} MB`,
          external: `${(memoryUsage.external / 1024 / 1024).toFixed(2)} MB`,
          arrayBuffers: `${(memoryUsage.arrayBuffers / 1024 / 1024).toFixed(2)} MB`
        };
        
        const configWithSystemInfo = {
          ...config,
          currentClient,
          featureFlags: featureFlagManager.getAll(),
          systemInfo: {
            ...systemInfo,
            memory
          }
        };
        
        console.error(`getConfig result: ${JSON.stringify(configWithSystemInfo, null, 2)}`);
        return {
          content: [{
            type: "text",
            text: `Current configuration:\n${JSON.stringify(configWithSystemInfo, null, 2)}`
          }],
        };
      } catch (error) {
        console.error(`Error in getConfig: ${error instanceof Error ? error.message : String(error)}`);
        console.error(error instanceof Error && error.stack ? error.stack : 'No stack trace available');
        // Return empty config rather than crashing
        return {
          content: [{
            type: "text",
            text: `Error getting configuration: ${error instanceof Error ? error.message : String(error)}\nUsing empty configuration.`
          }],
        };
      }
    }
  • The Zod schema for input arguments to the 'get_config' tool, which accepts no parameters.
    export const GetConfigArgsSchema = z.object({});
  • src/server.ts:191-210 (registration)
    Tool registration in the list_tools handler, defining the name, description, input schema, and annotations for the 'get_config' tool.
        name: "get_config",
        description: `
                Get the complete server configuration as JSON. Config includes fields for:
                - blockedCommands (array of blocked shell commands)
                - defaultShell (shell to use for commands)
                - allowedDirectories (paths the server can access)
                - fileReadLineLimit (max lines for read_file, default 1000)
                - fileWriteLineLimit (max lines per write_file call, default 50)
                - telemetryEnabled (boolean for telemetry opt-in/out)
                - currentClient (information about the currently connected MCP client)
                - clientHistory (history of all clients that have connected)
                - version (version of the DesktopCommander)
                - systemInfo (operating system and environment details)
                ${CMD_PREFIX_DESCRIPTION}`,
        inputSchema: zodToJsonSchema(GetConfigArgsSchema),
        annotations: {
            title: "Get Configuration",
            readOnlyHint: true,
        },
    },
  • Dispatch handler in the call_tool request handler that routes 'get_config' calls to the getConfig implementation function.
    case "get_config":
        try {
            result = await getConfig();
        } catch (error) {
            capture('server_request_error', { message: `Error in get_config handler: ${error}` });
            result = {
                content: [{ type: "text", text: `Error: Failed to get configuration` }],
                isError: true,
            };
        }
        break;
Behavior4/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds valuable context beyond annotations by detailing the specific fields included in the configuration (e.g., blockedCommands, defaultShell) and referencing invocation patterns ('DC: ...'), which helps the agent understand the tool's scope and usage context without contradicting annotations.

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

Conciseness4/5

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

The description is well-structured and front-loaded with the core purpose, followed by a bulleted list of fields and invocation notes. While slightly verbose due to the field listing, every sentence adds value (e.g., field details and usage reference), with no redundant information.

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

Completeness4/5

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

Given the tool's complexity (read-only configuration retrieval), annotations cover safety, and the description details the returned fields and invocation context. The lack of an output schema is mitigated by the field listing. However, it could briefly mention response format or error handling for full completeness.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the output semantics by listing the configuration fields returned, which compensates for the lack of an output schema, adding meaningful context beyond the empty input schema.

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

Purpose5/5

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

The description clearly states the specific action ('Get the complete server configuration as JSON') and resource ('server configuration'), distinguishing it from sibling tools like 'set_config_value' or 'get_usage_stats'. It explicitly lists the configuration fields included, making the purpose unambiguous.

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 by stating 'This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions,' which suggests a specific context for invoking the tool. However, it does not explicitly state when to use this tool versus alternatives like 'get_usage_stats' or 'set_config_value,' nor does it provide exclusions or prerequisites.

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/wonderwhy-er/ClaudeComputerCommander'

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