Skip to main content
Glama
devyhan

Xcode MCP Server

by devyhan

xcode-list-schemes

List all available build schemes in an Xcode project or workspace to help developers manage and select configurations for building, testing, and deploying iOS apps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesXcode 프로젝트 또는 워크스페이스 경로

Implementation Reference

  • The handler function for the 'xcode-list-schemes' tool. It determines if the project is a workspace or project, constructs the appropriate xcodebuild -list command, executes it using executeCommand, and returns the output as text content.
    async ({ projectPath }) => {
      try {
        console.error(`Xcode 스킴 목록 조회: ${projectPath}`);
        
        // 워크스페이스인지 프로젝트인지 확인
        let command;
        if (projectPath.endsWith(".xcworkspace")) {
          command = `xcodebuild -list -workspace "${projectPath}"`;
        } else {
          command = `xcodebuild -list -project "${projectPath}"`;
        }
        
        try {
          const { stdout, stderr } = await executeCommand(command);
          
          let resultText = "Xcode 스킴 및 타겟 목록:\n";
          if (stdout) resultText += `${stdout}\n`;
          if (stderr) resultText += `${stderr}\n`;
    
          return {
            content: [{ type: "text", text: resultText }]
          };
        } catch (error: any) {
          throw error;
        }
      } catch (error: any) {
        console.error(`스킴 목록 조회 오류: ${error.message}`);
        
        return {
          content: [{ 
            type: "text", 
            text: `스킴 목록을 조회하는 중 오류가 발생했습니다:\n${error.message}\n${error.stderr || ''}`
          }],
          isError: true
        };
      }
    }
  • Input schema for the 'xcode-list-schemes' tool, requiring a projectPath string parameter.
    {
      projectPath: z.string().describe("Xcode 프로젝트 또는 워크스페이스 경로")
  • src/index.ts:161-162 (registration)
    Registration of the 'xcode-list-schemes' tool using server.tool(name, schema, handler).
    server.tool(
      "xcode-list-schemes",
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