Best for
- Developers and teams using Swift who want structured output
- Agent workflows for build, test, and package automation
P
Pare Swift
Community
Structured Swift build, test, and package operations
- Category
- Dev Tools #315 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js >= 20
- Credentials
- No credential needed
- License
- MIT
- Last commit
44FMRS · D
Pare Swift provides concise JSON output, significantly reducing token usage, but the tool list and specifics need verification.
Strongest · Setup experience 11/20 Weakest · Reliability 6/20
Why each score
- Reliability 6/20
- The server manifest is structurally coherent, with name and version 0.22.0 matching npm package @paretools/swift, and stdio transport is explicit; a runnable server is plausible. However, the repository contains multiple MCP servers and no source code, tool declarations, committed tests, or CI artifacts for server-swift were supplied, so the init handshake, tool list, and actual behavior cannot be verified. The README is repository-level and cannot serve as reliable per-server evidence. Under the missing-evidence rule and static cap of 12, reliability is scored 6.
- Security and permissions 7/20
- No red-line indicators such as malware, credential theft, or covert exfiltration were found; the server runs locally over stdio and no network or credential handling is declared. Yet without source access, least-privilege design, confirmation for dangerous operations, and side effects of Swift build/test commands (e.g., package plugins or build scripts) cannot be assessed. Permission and confirmation coverage is incomplete, hence 7.
- Maintenance 11/20
- The repository is not archived, the MIT license is explicit, and manifest version 0.22.0 matches the npm package. README badges imply CI, code coverage, and OpenSSF checks, but these are unverified claims without supplied commit, release, or dependency-update history. It is also unclear whether any maintenance activity specifically covers server-swift rather than sibling servers, so full credit cannot be given; score is 11.
- Documentation 9/20
- The repository README is fairly comprehensive at project level, covering installation, client configuration guides, tool-filter environment variables, and general troubleshooting. However, for server-swift itself there is no list of actual tools, parameters, output schemas, usage limits, or the prerequisite of a pre-installed Swift toolchain. The referenced tool schemas and response examples were not supplied and cannot be used as evidence. This documentation gap warrants 9.
- Setup experience 11/20
- The manifest implies a straightforward install path via npm package @paretools/swift over stdio, and the README offers a swift preset plus client configuration guidance, so setup is few-step and plausible. However, no server-swift-specific configuration example is provided, the requirement for an installed Swift toolchain is not disclosed, and there is no committed CI/test evidence for this server. With the static cap at 15 and hidden prerequisites, setup is scored 11.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessReads local filesWrites / deletes local filesRuns commands or code
Not for
- Non-Swift projects
- Scenarios requiring an interactive Swift REPL
Required permissions
- Run Swift CLI commands such as swift build and swift test
- Access project files in the current working directory
Risks and side effects
- Executing build or test commands may have side effects, such as modifying files or consuming resources
- Depends on the local Swift toolchain; version mismatches may cause errors
Setup
Before you start
Runtime：Node.js >= 20
Other optional settings (1)
PARE_TOOLS
Optional universal filter in server:tool format that limits registered tools across all Pare servers; takes precedence over per-server variables.
Install via npm: npm install -g @paretools/swift. Then configure the server in your MCP client with the command npx -y @paretools/swift.
Check that it works
Confirm the Pare Swift server's build/test tools appear in your client's tool list after connection, or run npx @paretools/init doctor to validate the setup.
Troubleshooting
- Ensure Node.js >= 20
- Ensure the Swift toolchain is installed and accessible
- Check MCP client configuration
Things to try
Once connected, you can ask your AI assistant things like:
- Build the current Swift package and report any errors.
- Run the Swift package tests and give me a structured summary.
- Show me the dependency info for this Swift package.
Use cases
Automate Swift project builds, tests, and package tasks
Provide reliable Swift tool output to AI agents
Overview
Pare Swift is one of the Pare MCP servers, providing structured build, test, and package management operations for Swift, returning typed JSON instead of raw terminal text. It wraps the Swift toolchain to give AI agents reliable, structured data.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method