npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

automerge-swift-mcp

v1.3.2

Published

MCP server for Automerge Swift skills, prompts, and vendored docs from any MCP-compatible AI coding tool

Readme

Automerge Swift MCP Server

MCP server that brings Automerge Swift documentation, skills, and command entrypoints to any MCP-compatible AI coding tool — VS Code with GitHub Copilot, Claude Desktop, Cursor, Gemini CLI, OpenCode, and more.

What You Get

The MCP server exposes Automerge Swift guidance through the MCP protocol:

  • 8 toolssearch_skills, read_skill, get_catalog, list_skills, list_docs, search_docs, search_symbols, get_doc
  • MCP resources for each skill and documentation page
  • 2 MCP promptsask and audit
  • Full-text search across skill metadata, DocC articles, and source-derived symbol docs

Prerequisites

  • Node.js 18+ — check with node --version

That's it.

Installation by Tool

Each tool needs a configuration snippet that tells it how to launch the MCP server.

VS Code + GitHub Copilot

Add to your VS Code settings.json:

{
  "github.copilot.chat.mcp.servers": {
    "automerge-swift": {
      "command": "npx",
      "args": ["-y", "automerge-swift-mcp"]
    }
  }
}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "automerge-swift": {
      "command": "npx",
      "args": ["-y", "automerge-swift-mcp"]
    }
  }
}

Cursor

Add to .cursor/mcp.json in your workspace:

{
  "mcpServers": {
    "automerge-swift": {
      "command": "npx",
      "args": ["-y", "automerge-swift-mcp"]
    }
  }
}

Gemini CLI

Add to ~/.gemini/config.toml:

[[mcp_servers]]
name = "automerge-swift"
command = "npx"
args = ["-y", "automerge-swift-mcp"]

OpenCode

Add to opencode.jsonc in your project root (or ~/.config/opencode/opencode.jsonc for global):

{
  "mcp": {
    "automerge-swift": {
      "type": "local",
      "command": ["npx", "-y", "automerge-swift-mcp"]
    }
  }
}

Local Clone (Any Tool)

If you cloned the repo instead of installing from npm:

{
  "mcpServers": {
    "automerge-swift": {
      "command": "node",
      "args": ["/path/to/automerge-swift-skills/src/server.mjs"]
    }
  }
}

Configuration

Environment Variables

| Variable | Values | Default | Description | |----------|--------|---------|-------------| | AUTOMERGE_SWIFT_DOCS_AUTO_SYNC | 0, 1 | 1 in repo clone, forced to 0 in npm package | Auto-refresh docs from local checkout on startup | | AUTOMERGE_SWIFT_REPO | File path | /tmp/automerge-swift | Path to local automerge-swift checkout | | AUTOMERGE_SWIFT_DOCS_DEBUG_LOG | File path | — | Write debug log to this file |

Verify It Works

Quick Test

Run the server directly to confirm it launches without errors:

npx automerge-swift-mcp

The server should start and wait for stdin input (MCP uses stdio transport). Press Ctrl+C to stop.

MCP Inspector

For interactive testing, use the official MCP Inspector:

npx @modelcontextprotocol/inspector npx automerge-swift-mcp

This opens a web UI where you can browse resources, test prompts and tools, and search docs.

In Your Tool

Once configured, try asking your AI tool:

"Search the Automerge Swift docs for Document"

It should find the right skill via search_skills and return relevant guidance.

Available Tools

| Tool | Description | |------|-------------| | search_skills | BM25 ranked search with matching sections | | read_skill | Read skill content with optional section filtering | | get_catalog | Browse skills organized by category | | list_skills | List all Automerge Swift skills | | list_docs | List all vendored documentation pages, optionally filtered by module or source kind | | search_docs | Full-text search across all documentation pages | | search_symbols | Search only source-derived public Swift symbol docs | | get_doc | Retrieve a specific documentation page by ID, URI, or title |

Troubleshooting

Server Won't Start

Check Node version — must be 18+:

node --version

No Search Results

The server reads vendored docs from vendor/automerge-swift/. If this directory is empty, run:

npm run sync-docs

Client Can't Connect

MCP uses stdin/stdout for communication. Common issues:

  • Wrong config — ensure command is "npx" and args is ["-y", "automerge-swift-mcp"]
  • Other stdout writers — make sure nothing else writes to stdout; logs go to stderr only

Test the command from your config manually:

npx automerge-swift-mcp
# Should start without errors, waiting for stdin

License

MIT