Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_schemes

Retrieve all available build schemes from an Xcode project or workspace to configure development workflows and testing environments.

Instructions

List all available schemes in an Xcode project or workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to the Xcode project (.xcodeproj) or workspace (.xcworkspace)

Implementation Reference

  • Handler function that validates the project path, executes xcodebuild -list command, parses the output using parseXcodebuildOutput, and returns formatted scheme list.
    async listSchemes(args: ListSchemesArgs): Promise<any> {
      const { projectPath } = args;
    
      if (!projectPath) {
        throw new Error('Project path is required');
      }
    
      if (!existsSync(projectPath)) {
        throw new Error(`Project path does not exist: ${projectPath}`);
      }
    
      const stats = statSync(projectPath);
      if (!stats.isDirectory()) {
        throw new Error(`Project path is not a directory: ${projectPath}`);
      }
    
      const isWorkspace = projectPath.endsWith('.xcworkspace');
      const isProject = projectPath.endsWith('.xcodeproj');
    
      if (!isWorkspace && !isProject) {
        throw new Error('Project path must be either a .xcworkspace or .xcodeproj file');
      }
    
      try {
        const command = isWorkspace 
          ? `xcodebuild -workspace "${projectPath}" -list`
          : `xcodebuild -project "${projectPath}" -list`;
    
        const { stdout, stderr } = await execAsync(command);
    
        if (stderr && stderr.trim() !== '') {
          console.error('xcodebuild stderr:', stderr);
        }
    
        const schemes = this.parseXcodebuildOutput(stdout);
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                projectPath,
                projectType: isWorkspace ? 'workspace' : 'project',
                schemes,
                totalSchemes: schemes.length
              }, null, 2)
            }
          ]
        };
      } catch (error: any) {
        throw new Error(`Failed to list schemes: ${error.message}`);
      }
    }
  • Private helper method to parse xcodebuild -list output and extract scheme names and shared status.
    private parseXcodebuildOutput(output: string): SchemeInfo[] {
      const lines = output.split('\n');
      const schemes: SchemeInfo[] = [];
      let inSchemesSection = false;
    
      for (const line of lines) {
        const trimmedLine = line.trim();
        
        if (trimmedLine === 'Schemes:') {
          inSchemesSection = true;
          continue;
        }
    
        if (inSchemesSection) {
          if (trimmedLine === '' || trimmedLine.startsWith('Build Configurations:') || trimmedLine.startsWith('If no build configuration')) {
            break;
          }
    
          if (trimmedLine && !trimmedLine.startsWith('Information about project')) {
            const isShared = !trimmedLine.startsWith('    ');
            const schemeName = trimmedLine.trim();
            
            if (schemeName) {
              schemes.push({
                name: schemeName,
                isShared
              });
            }
          }
        }
      }
    
      return schemes;
    }
  • TypeScript interface defining the input arguments for listSchemes handler (projectPath: string).
    export interface ListSchemesArgs {
      projectPath: string;
    }
  • src/index.ts:836-848 (registration)
    Tool registration in buildToolsList(): defines name 'list_schemes', description, and inputSchema matching ListSchemesArgs.
      name: "list_schemes",
      description: "List all available schemes in an Xcode project or workspace",
      inputSchema: {
        type: "object",
        properties: {
          projectPath: {
            type: "string",
            description: "Path to the Xcode project (.xcodeproj) or workspace (.xcworkspace)"
          }
        },
        required: ["projectPath"]
      }
    },
  • src/index.ts:1419-1421 (registration)
    Dispatch registration in setupHandlers() switch statement: maps 'list_schemes' tool calls to xcodeHandlers.listSchemes.
    case "list_schemes":
      return { toolResult: await this.xcodeHandlers.listSchemes(args as any) };
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, potential side effects, error conditions, or output format, which is inadequate for a tool with no annotation coverage.

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 with zero waste. It's appropriately sized and front-loaded with the core purpose, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is minimally adequate but lacks depth. It explains what the tool does but omits behavioral context and usage guidance, which are important even for simple tools.

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 the schema already documents the single parameter. The description adds no additional meaning about the parameter beyond what the schema provides, maintaining the baseline score for high schema coverage.

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 verb ('List') and resource ('all available schemes'), specifying the context ('in an Xcode project or workspace'). It distinguishes from siblings by focusing on schemes, but doesn't explicitly differentiate from similar list tools like list_apps or list_bundle_ids beyond the resource type.

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. The description doesn't mention prerequisites, timing, or comparisons to other tools, leaving the agent to infer usage solely from the purpose.

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/concavegit/app-store-connect-mcp-server'

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