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

xerant-mcp-server

v0.1.0

Published

MCP server bridging OpenCode and other MCP clients to the Xerant internal DevOps API. Exposes 22 tools for local-compose deploys, GitHub-repo deploys, container lifecycle, and log tailing.

Downloads

108

Readme

@xerant/mcp-server

Model Context Protocol bridge between OpenCode (or any MCP client) and the Xerant internal DevOps API.

OpenCode ── stdio ──▶ xerant-mcp (this package) ── HTTP ──▶ internal-server (FastAPI) ──▶ Docker

Install & build

cd mcp-server
npm install
npm run build

This produces an executable at dist/index.js.

Environment

| Var | Default | Purpose | |-----|---------|---------| | XERANT_API_URL | http://localhost:8000 | Base URL of the internal-server FastAPI service | | XERANT_API_KEY | (unset) | Optional bearer token forwarded on every request | | XERANT_API_TIMEOUT_MS | 60000 | Per-request timeout |

The API key is only sent as Authorization: Bearer <key>. It is never written to disk, logged, or echoed.

Register in OpenCode

Add to your opencode.json (workspace-level or ~/.config/opencode/opencode.json):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xerant": {
      "type": "local",
      "command": ["node", "./mcp-server/dist/index.js"],
      "environment": {
        "XERANT_API_URL": "{env:XERANT_API_URL}",
        "XERANT_API_KEY": "{env:XERANT_API_KEY}"
      },
      "enabled": true
    }
  }
}

If you prefer running from source without a build step, swap the command for:

"command": ["npx", "-y", "tsx", "./mcp-server/src/index.ts"]

Tools exposed

| Tool | Maps to | |------|---------| | xerant_health | GET /health | | xerant_docker_health | GET /health/docker | | xerant_deploy | POST /deployments | | xerant_list_deployments | GET /deployments | | xerant_get_deployment | GET /deployments/{id} | | xerant_deployment_logs | GET /deployments/{id}/logs | | xerant_stop_deployment | POST /deployments/{id}/stop | | xerant_start_deployment | POST /deployments/{id}/start | | xerant_restart_deployment | POST /deployments/{id}/restart | | xerant_redeploy | POST /deployments/{id}/redeploy | | xerant_remove_deployment | DELETE /deployments/{id} | | xerant_list_containers | GET /containers | | xerant_get_container | GET /containers/{id} | | xerant_container_logs | GET /containers/{id}/logs | | xerant_github_get_repo | GET /github/repos/{owner}/{repo} | | xerant_github_list_branches | GET /github/repos/{owner}/{repo}/branches | | xerant_github_get_file | GET /github/repos/{owner}/{repo}/contents/{path}?ref=... |

xerant_deploy mapping details

The tool accepts an environment argument (prod|staging|preview|dev or their long forms) that the server itself does not understand. The bridge maps it to:

  • env.DEPLOY_ENV = <canonical> injected into the runtime env
  • name = <repo-name>-<canonical> derived automatically (override with explicit name)

Development

# Run from source with hot reload (stdio client will still attach)
npm run dev

# Typecheck only
npm run typecheck

# Manual smoke test: call the `tools/list` method over stdio
node dist/index.js
# paste: {"jsonrpc":"2.0","id":1,"method":"tools/list"}\n