# a-25/ios-mcp-code-quality-server [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/a-25/ios-mcp-code-quality-server  
**GitHub Stars:** 10  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/a-25-ios-mcp-code-quality-server

## Description
iOS code quality analysis and test automation server. Provides comprehensive Xcode test execution, SwiftLint integration, and detailed failure analysis. Operates in both CLI and MCP server modes for direct developer usage and AI assistant integration.

## Tools
Capabilities this server exposes over MCP:

- **Note** — Either `xcodeproj` or `xcworkspace` parameter is mandatory (at least one must be provided)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "ios-mcp-code-quality-server": {
    "command": "npx",
    "args": ["-y","-"]
  }
}
```

## Documentation

## What a-25/ios-mcp-code-quality-server MCP server does

The a-25/ios-mcp-code-quality-server MCP server provides two related workflows for iOS development: Xcode test execution and SwiftLint-based analysis. It can be used directly from a terminal or started as an MCP server for an AI assistant. Test results include failure analysis and build-error information, while lint results can identify issues in selected Swift files and report file locations and line numbers.

The test workflow supports either an Xcode project or workspace, but at least one of `xcodeproj` or `xcworkspace` must be supplied. A scheme is also required. The lint workflow accepts a comma-separated list of changed files and can use a custom SwiftLint configuration file.

## How it works

With command-line arguments, the package selects CLI mode. The `test` command invokes iOS tests and accepts options for a simulator or other destination, JSON output, and verbose logging. The `lint` command analyzes the specified files and supports JSON output, verbose logging, and a custom configuration path.

When started without arguments, the package enters MCP server mode. The explicit `server` command does the same and can accept a port option. The documented default is port 3000. MCP responses are structured for consumption by an AI assistant, while CLI output can be human-readable or JSON for scripts and CI workflows.

## Setup and configuration

The a-25/ios-mcp-code-quality-server MCP server requires Node.js 18 or newer. Xcode is needed for project building and testing, and an iOS Simulator or physical device is needed to run tests. SwiftLint is optional and is used for lint analysis.

The documented quick-start path uses `npx ios-mcp-code-quality-server` for either CLI commands or server startup. A source checkout can instead be installed with `npm install`, built with `npm run build`, and started with `npm start` or `node dist/index.js server`.

Configuration is available through environment variables. `PORT` sets the listening port and defaults to `3000`; `NODE_ENV` defaults to `development`; and `LOG_LEVEL` defaults to `info`. Additional documented settings cover server identity, allowed hosts, rate limits, session cleanup, and concurrent task limits.

## Tools and capabilities

The documented MCP capabilities include:

- Executing iOS tests for an Xcode project or workspace.
- Selecting a test scheme and destination.
- Returning detailed test failure and build-error analysis.
- Running SwiftLint against specified changed files.
- Applying a supplied SwiftLint configuration path.
- Producing structured or JSON-oriented results for assistant and automation workflows.

## Limitations and notes

This server is designed for local iOS development environments rather than a hosted testing service. Its test functions depend on Xcode and an available iOS runtime or device. SwiftLint analysis depends on SwiftLint being installed. Test requests cannot omit both project inputs: either `xcodeproj` or `xcworkspace` is mandatory.

The README shows an HTTP endpoint at `http://localhost:3000` for assistant configuration. It names Claude and Copilot as example assistant integrations but does not provide client-specific setup for every MCP application. All analysis is described as taking place on the local machine.

The a-25/ios-mcp-code-quality-server MCP server exposes configuration defaults, but the provided material does not identify any required API keys or external paid services.

_Full upstream README: https://allmcps.com/mcp/a-25-ios-mcp-code-quality-server/readme_