Skip to main content
Glama
devyhan

Xcode MCP Server

by devyhan

swift-package-manager

Manage Swift packages in Xcode projects by executing SPM commands like init, update, resolve, reset, and clean to handle dependencies and build configurations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesSPM 명령어 (init, update, resolve, reset, clean)
packageDirYesSwift Package 디렉토리 경로
extraArgsNo추가 SPM 인자들

Implementation Reference

  • Executes the Swift Package Manager tool logic by constructing a shell command to run 'swift package [command]' in the specified package directory, handling extra arguments, executing via executeCommand, and formatting stdout/stderr output or error response.
    async ({ command, packageDir, extraArgs = [] }) => {
      try {
        console.error(`Swift Package Manager 명령 실행: ${command} in ${packageDir}`);
        
        let spmCommand = `cd "${packageDir}" && swift package ${command}`;
        
        // 추가 인자 추가
        if (extraArgs.length > 0) {
          spmCommand += " " + extraArgs.join(" ");
        }
        
        console.error(`실행할 SPM 명령어: ${spmCommand}`);
        
        // 명령어 실행
        try {
          const { stdout, stderr } = await executeCommand(spmCommand);
          
          let resultText = "Swift Package Manager 결과:\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(`Swift Package Manager 오류: ${error.message}`);
        
        return {
          content: [{ 
            type: "text", 
            text: `Swift Package Manager 명령 실행 중 오류가 발생했습니다:\n${error.message}\n${error.stderr || ''}`
          }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the swift-package-manager tool: command (enum), packageDir (string), and optional extraArgs (array of strings).
      command: z.enum(["init", "update", "resolve", "reset", "clean"]).describe("SPM 명령어 (init, update, resolve, reset, clean)"),
      packageDir: z.string().describe("Swift Package 디렉토리 경로"),
      extraArgs: z.array(z.string()).optional().describe("추가 SPM 인자들")
    },
  • src/index.ts:450-496 (registration)
    Registers the swift-package-manager tool on the MCP server with its schema and handler function.
    server.tool(
      "swift-package-manager",
      {
        command: z.enum(["init", "update", "resolve", "reset", "clean"]).describe("SPM 명령어 (init, update, resolve, reset, clean)"),
        packageDir: z.string().describe("Swift Package 디렉토리 경로"),
        extraArgs: z.array(z.string()).optional().describe("추가 SPM 인자들")
      },
      async ({ command, packageDir, extraArgs = [] }) => {
        try {
          console.error(`Swift Package Manager 명령 실행: ${command} in ${packageDir}`);
          
          let spmCommand = `cd "${packageDir}" && swift package ${command}`;
          
          // 추가 인자 추가
          if (extraArgs.length > 0) {
            spmCommand += " " + extraArgs.join(" ");
          }
          
          console.error(`실행할 SPM 명령어: ${spmCommand}`);
          
          // 명령어 실행
          try {
            const { stdout, stderr } = await executeCommand(spmCommand);
            
            let resultText = "Swift Package Manager 결과:\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(`Swift Package Manager 오류: ${error.message}`);
          
          return {
            content: [{ 
              type: "text", 
              text: `Swift Package Manager 명령 실행 중 오류가 발생했습니다:\n${error.message}\n${error.stderr || ''}`
            }],
            isError: true
          };
        }
      }
    );
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