Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
117 lines (82 loc) · 2.52 KB

CONTRIBUTING.md

File metadata and controls

117 lines (82 loc) · 2.52 KB

Contributing

Contributions are welcome! Here's how you can help improve XcodeBuildMCP.

Local development setup

Prerequisites

In addition to the prerequisites mentioned in the Getting started section of the README, you will also need:

  • Node.js (v18 or later)
  • npm

Optional: Enabling UI Automation

When running locally, you'll need to install Facebook's idb tools:

# Install idb_companion (required for UI automation)
brew tap facebook/fb
brew install idb-companion

Install fb-idb Python package:

pip install fb-idb==1.1.7

Installation

  1. Clone the repository
  2. Install dependencies: 
    npm install
  3. Build the project: 
    npm run build
  4. Start the server: 
    node build/index.js

Configure your MCP client

To configure your MCP client to use your local XcodeBuildMCP server you can use the following configuration:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "node",
      "args": [
        "/path_to/XcodeBuildMCP/build/index.js"
      ]
    }
  }
}

Debugging

You can use MCP Inspector via:

npm run inspect

or if you prefer the explict command:

npx @modelcontextprotocol/inspector node build/index.js

Using the diagnostic tool

Running the XcodeBuildMCP server with the environmental variable XCODEBUILDMCP_DEBUG=true will expose a new diagnostic tool which you can run using MCP Inspector:

XCODEBUILDMCP_DEBUG=true npm run inspect

Alternatively, you can run the diagnostic tool directly:

node build/diagnostic-cli.js

Making changes

  1. Fork the repository and create a new branch
  2. Follow the TypeScript best practices and existing code style
  3. Add proper parameter validation and error handling

Testing

  1. Build the project with npm run build
  2. Test your changes with MCP Inspector
  3. Verify tools work correctly with different MCP clients

Submitting

  1. Run npm run lint to check for linting issues (use npm run lint:fix to auto-fix)
  2. Run npm run format:check to verify formatting (use npm run format to fix)
  3. Update documentation if you've added or modified features
  4. Add your changes to the CHANGELOG.md file
  5. Push your changes and create a pull request with a clear description
  6. Link any related issues

For major changes or new features, please open an issue first to discuss your proposed changes.

Code of Conduct

Please follow our Code of Conduct and community guidelines.