Skip to main content
Glama
ebowwa

Xcode MCP Server

by ebowwa

xcode_show_build_settings

Display build settings for Xcode projects and schemes to configure compilation parameters and project configurations.

Instructions

Show build settings for a project/scheme

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYesPath to .xcodeproj file
schemeYesScheme name

Implementation Reference

  • MCP CallToolRequestSchema handler that dispatches 'xcode_*' tool calls to CommandExecutor.executeCommand after stripping the 'xcode_' prefix. This is the entry point for executing the tool.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        // Handle web monitor tools
        if (name === 'start_web_monitor') {
          const result = await this.webMonitorManager.start();
          return {
            content: [
              {
                type: 'text',
                text: `${result.message}\n\nWeb interface available at: ${result.url}`
              }
            ]
          };
        }
        
        if (name === 'stop_web_monitor') {
          const result = this.webMonitorManager.stop();
          return {
            content: [
              {
                type: 'text',
                text: result.message
              }
            ]
          };
        }
        
        if (name === 'web_monitor_status') {
          const status = this.webMonitorManager.getStatus();
          let text = status.running 
            ? `Web monitor is running at ${status.url} (port ${status.port})`
            : 'Web monitor is not running';
          return {
            content: [
              {
                type: 'text',
                text: text
              }
            ]
          };
        }
        
        // Handle Xcode commands
        // Remove 'xcode_' prefix if present
        const commandName = name.startsWith('xcode_') ? name.slice(6) : name;
        const result = await this.commandExecutor.executeCommand(commandName, args);
        
        let responseText = result.output;
        if (result.error) {
          responseText += `\n\nWarnings/Errors:\n${result.error}`;
        }
        if (!result.success) {
          responseText = `Command failed: ${result.error}\n\nCommand executed: ${result.command}`;
        }
        
        return {
          content: [
            {
              type: 'text',
              text: responseText,
            },
          ],
        };
      } catch (error) {
        if (error instanceof McpError) {
          throw error;
        }
        
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${errorMessage}`,
            },
          ],
        };
      }
    });
  • Core execution logic for commands (including 'show_build_settings'). Validates parameters, builds shell command template, executes via child_process.execAsync, and returns output/error. This implements the tool logic generically.
    async executeCommand(name: string, args: Record<string, any> = {}): Promise<{
      success: boolean;
      output: string;
      error?: string;
      command: string;
    }> {
      const command = this.getCommand(name);
      if (!command) {
        throw new Error(`Command '${name}' not found`);
      }
    
      this.validateParameters(command, args);
    
      // Handle internal commands
      if (command.command.startsWith('internal:')) {
        return await this.executeInternalCommand(command, args);
      }
    
      // Handle external commands
      const builtCommand = this.buildCommand(command, args);
    
      try {
        const { stdout, stderr } = await execAsync(builtCommand);
        
        return {
          success: true,
          output: stdout,
          error: stderr || undefined,
          command: builtCommand
        };
      } catch (error) {
        return {
          success: false,
          output: '',
          error: error instanceof Error ? error.message : String(error),
          command: builtCommand
        };
      }
    }
  • Generates the input schema and metadata for MCP tools like 'xcode_show_build_settings' from loaded command definitions.
    // Generate MCP tool definitions from commands
    generateMCPToolDefinitions(): Array<{
      name: string;
      description: string;
      inputSchema: any;
    }> {
      return Object.entries(this.commands).map(([name, command]) => ({
        name: `xcode_${name}`,
        description: command.description,
        inputSchema: {
          type: 'object',
          properties: command.parameters ? Object.fromEntries(
            Object.entries(command.parameters).map(([paramName, paramDef]) => [
              paramName,
              {
                type: paramDef.type,
                description: paramDef.description,
                ...(paramDef.default !== undefined && { default: paramDef.default })
              }
            ])
          ) : {},
          required: command.parameters ? Object.entries(command.parameters)
            .filter(([_, paramDef]) => paramDef.required)
            .map(([paramName]) => paramName) : []
        }
      }));
    }
  • src/index.ts:87-89 (registration)
    Registers the list of available tools (including all generated xcode_* tools) for MCP ListToolsRequestSchema.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [...tools, ...webMonitorTools],
    }));
  • Helper function that constructs the actual shell command string from the command template and parameters, used in tool execution.
    buildCommand(command: XcodeCommand, args: Record<string, any>): string {
      let builtCommand = command.command;
    
      // Replace required parameters
      if (command.parameters) {
        for (const [paramName, paramDef] of Object.entries(command.parameters)) {
          const value = args[paramName] !== undefined ? args[paramName] : paramDef.default;
          
          if (paramDef.type === 'boolean') {
            // Handle boolean parameters
            if (value === true) {
              // Replace placeholder with the template if true
              builtCommand = builtCommand.replace(`{${paramName}}`, paramDef.template || '');
            } else {
              // Remove placeholder if false
              builtCommand = builtCommand.replace(`{${paramName}}`, '');
            }
          } else if (value !== undefined && value !== null && value !== '') {
            if (paramDef.template) {
              // Use custom template for parameter
              const paramValue = paramDef.template.replace(`{${paramName}}`, value);
              builtCommand = builtCommand.replace(`{${paramName}}`, paramValue);
            } else {
              // Direct replacement
              builtCommand = builtCommand.replace(`{${paramName}}`, value);
            }
          } else {
            // Remove optional parameter placeholders
            builtCommand = builtCommand.replace(new RegExp(`\\s*\\{${paramName}\\}`, 'g'), '');
          }
        }
      }
    
      // Clean up any remaining placeholder patterns
      builtCommand = builtCommand.replace(/\s+/g, ' ').trim();
      
      return builtCommand;
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose if this is a read-only operation, what output format to expect (e.g., text, JSON), error conditions, or dependencies, which are critical for a tool with no output schema.

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 directly states the tool's function without unnecessary words. It's front-loaded and appropriately sized for its purpose, earning full marks for conciseness.

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 lacks details on behavior, output format, error handling, or integration with siblings (e.g., how it relates to 'xcode_list_schemes'), making it inadequate for an agent to use effectively without guesswork.

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%, so parameters are fully documented in the schema. The description adds no additional meaning beyond implying the parameters are used to identify the target, meeting the baseline of 3 without compensating value.

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 action ('Show') and target ('build settings for a project/scheme'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'xcode_list_schemes' or 'xcode_show_destinations' that also display information, missing specific scope details that would warrant a 5.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid Xcode project), exclusions, or related tools like 'xcode_list_schemes' for scheme discovery, leaving the agent without usage context.

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/ebowwa/xcode-mcp'

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