Skip to main content
Glama
devyhan

Xcode MCP Server

by devyhan

xcode-build

Build Xcode projects and workspaces with specified schemes, configurations, and destinations to generate iOS app binaries for testing or deployment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesXcode 프로젝트 또는 워크스페이스 경로
schemeYes빌드할 스킴
configurationNo빌드 구성 (예: Debug, Release)
destinationNo빌드 대상 (예: 'platform=iOS Simulator,name=iPhone 14')
extraArgsNo추가 xcodebuild 인자들
outputDirNo빌드 결과물 저장 경로 (SYMROOT)
cleanNo빌드 전 clean 실행 여부

Implementation Reference

  • The handler function that constructs the xcodebuild command based on input parameters and executes it using executeCommand, returning build results or errors.
    async ({ projectPath, scheme, configuration, destination, extraArgs = [], outputDir, clean = false }) => {
      try {
        console.error(`Xcode 프로젝트 빌드: ${projectPath}, Scheme: ${scheme}`);
        
        let command = `xcodebuild`;
        
        // 워크스페이스인지 프로젝트인지 확인
        if (projectPath.endsWith(".xcworkspace")) {
          command += ` -workspace "${projectPath}"`;
        } else {
          command += ` -project "${projectPath}"`;
        }
        
        command += ` -scheme "${scheme}"`;
        
        if (clean) {
          command += ` clean`;
        }
        
        command += ` build`; // 명시적으로 build 액션 지정
        
        if (configuration) {
          command += ` -configuration "${configuration}"`;
        }
        
        if (destination) {
          command += ` -destination "${destination}"`;
        }
        
        if (outputDir) {
          command += ` SYMROOT="${outputDir}"`;
        }
        
        // 추가 인자 추가
        if (extraArgs.length > 0) {
          command += " " + extraArgs.join(" ");
        }
        
        console.error(`실행할 빌드 명령어: ${command}`);
        
        // 빌드 명령어 실행
        try {
          const { stdout, stderr } = await executeCommand(command);
          
          let resultText = "빌드 결과:\n";
          if (stdout) resultText += `${stdout}\n`;
          if (stderr) resultText += `STDERR:\n${stderr}\n`;
    
          return {
            content: [{ type: "text", text: resultText }]
          };
        } catch (error: any) {
          throw error;
        }
      } catch (error: any) {
        console.error(`Xcode 빌드 오류: ${error.message}`);
        
        return {
          content: [{ 
            type: "text", 
            text: `Xcode 빌드 중 오류가 발생했습니다:\n${error.message}\n${error.stderr || ''}`
          }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the xcode-build tool.
    {
      projectPath: z.string().describe("Xcode 프로젝트 또는 워크스페이스 경로"),
      scheme: z.string().describe("빌드할 스킴"),
      configuration: z.string().optional().describe("빌드 구성 (예: Debug, Release)"),
      destination: z.string().optional().describe("빌드 대상 (예: 'platform=iOS Simulator,name=iPhone 14')"),
      extraArgs: z.array(z.string()).optional().describe("추가 xcodebuild 인자들"),
      outputDir: z.string().optional().describe("빌드 결과물 저장 경로 (SYMROOT)"),
      clean: z.boolean().optional().describe("빌드 전 clean 실행 여부")
  • src/index.ts:81-158 (registration)
    Registration of the xcode-build tool using server.tool, including name, schema, and inline handler.
    server.tool(
      "xcode-build",
      {
        projectPath: z.string().describe("Xcode 프로젝트 또는 워크스페이스 경로"),
        scheme: z.string().describe("빌드할 스킴"),
        configuration: z.string().optional().describe("빌드 구성 (예: Debug, Release)"),
        destination: z.string().optional().describe("빌드 대상 (예: 'platform=iOS Simulator,name=iPhone 14')"),
        extraArgs: z.array(z.string()).optional().describe("추가 xcodebuild 인자들"),
        outputDir: z.string().optional().describe("빌드 결과물 저장 경로 (SYMROOT)"),
        clean: z.boolean().optional().describe("빌드 전 clean 실행 여부")
      },
      async ({ projectPath, scheme, configuration, destination, extraArgs = [], outputDir, clean = false }) => {
        try {
          console.error(`Xcode 프로젝트 빌드: ${projectPath}, Scheme: ${scheme}`);
          
          let command = `xcodebuild`;
          
          // 워크스페이스인지 프로젝트인지 확인
          if (projectPath.endsWith(".xcworkspace")) {
            command += ` -workspace "${projectPath}"`;
          } else {
            command += ` -project "${projectPath}"`;
          }
          
          command += ` -scheme "${scheme}"`;
          
          if (clean) {
            command += ` clean`;
          }
          
          command += ` build`; // 명시적으로 build 액션 지정
          
          if (configuration) {
            command += ` -configuration "${configuration}"`;
          }
          
          if (destination) {
            command += ` -destination "${destination}"`;
          }
          
          if (outputDir) {
            command += ` SYMROOT="${outputDir}"`;
          }
          
          // 추가 인자 추가
          if (extraArgs.length > 0) {
            command += " " + extraArgs.join(" ");
          }
          
          console.error(`실행할 빌드 명령어: ${command}`);
          
          // 빌드 명령어 실행
          try {
            const { stdout, stderr } = await executeCommand(command);
            
            let resultText = "빌드 결과:\n";
            if (stdout) resultText += `${stdout}\n`;
            if (stderr) resultText += `STDERR:\n${stderr}\n`;
    
            return {
              content: [{ type: "text", text: resultText }]
            };
          } catch (error: any) {
            throw error;
          }
        } catch (error: any) {
          console.error(`Xcode 빌드 오류: ${error.message}`);
          
          return {
            content: [{ 
              type: "text", 
              text: `Xcode 빌드 중 오류가 발생했습니다:\n${error.message}\n${error.stderr || ''}`
            }],
            isError: true
          };
        }
      }
    );
  • Helper function imported and used by the xcode-build handler to safely execute the constructed xcodebuild shell command.
    export async function executeCommand(command: string, workingDir?: string, timeout: number = 60000) {
      try {
        console.error(`명령어 실행: ${command} in ${workingDir || 'current directory'}`);
        
        // 보안 상의 이유로 위험한 명령어 필터링
        if (/rm\s+-rf\s+\//.test(command) || /mkfs/.test(command) || /dd\s+if/.test(command)) {
          throw new Error("보안상의 이유로 이 명령어를 실행할 수 없습니다.");
        }
    
        const options = {
          cwd: workingDir,
          timeout: timeout,
          // 버퍼 제한 제거
          maxBuffer: Infinity
        };
    
        const { stdout, stderr } = await execPromise(command, options);
        return { stdout, stderr };
      } catch (error: any) {
        console.error(`명령어 실행 오류: ${error.message}`);
        throw error;
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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