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

@enfyra/mcp-server

v0.2.10

Published

MCP server for Enfyra - manage Enfyra instances from MCP-compatible coding tools

Readme

Enfyra MCP Server

Connect Enfyra to MCP-compatible coding tools such as Codex, Claude Code, Cursor, VS Code / GitHub Copilot, Google Antigravity, ZCode, and other STDIO MCP hosts.

Install and Configure

Run this from the project that should use Enfyra:

npx @enfyra/mcp-server@latest config

The setup asks for:

  • the Enfyra app/admin URL, such as http://localhost:3000 or https://demo.enfyra.io;
  • an ENFYRA_API_TOKEN created from the Enfyra admin UI /me page;
  • the MCP clients to configure.

It writes project-local configuration and replaces only the enfyra server entry.

| Client | Command | Project config | |---|---|---| | Codex | npx @enfyra/mcp-server@latest config --codex | .codex/config.toml | | Claude Code | npx @enfyra/mcp-server@latest config --claude-code | .mcp.json | | Cursor | npx @enfyra/mcp-server@latest config --cursor | .cursor/mcp.json | | VS Code / GitHub Copilot | npx @enfyra/mcp-server@latest config --vscode | .vscode/mcp.json | | Google Antigravity | npx @enfyra/mcp-server@latest config --antigravity | .agents/mcp_config.json | | ZCode | npx @enfyra/mcp-server@latest config --zcode | .zcode/config.json |

Non-interactive setup for all supported clients:

npx @enfyra/mcp-server@latest config --yes \
  --app-url http://localhost:3000 \
  --api-token efy_pat_your-token

Remove temporary source artifacts and local telemetry files created by MCP:

npx @enfyra/mcp-server@latest cleanup

Configure more than one selected client:

npx @enfyra/mcp-server@latest config --cursor --claude-code

Manual Configuration

For hosts that accept an mcpServers JSON block:

{
  "mcpServers": {
    "enfyra": {
      "command": "npx",
      "args": ["-y", "@enfyra/mcp-server@latest"],
      "env": {
        "ENFYRA_API_URL": "http://localhost:3000/api",
        "ENFYRA_API_TOKEN": "efy_pat_your-token"
      }
    }
  }
}

Codex project configuration uses TOML:

[mcp_servers.enfyra]
command = "npx"
args = ["-y", "@enfyra/mcp-server@latest"]

[mcp_servers.enfyra.env]
ENFYRA_API_URL = "http://localhost:3000/api"
ENFYRA_API_TOKEN = "efy_pat_your-token"

ZCode uses a nested mcp.servers JSON structure in .zcode/config.json:

{
  "mcp": {
    "servers": {
      "enfyra": {
        "command": "npx",
        "args": ["-y", "@enfyra/mcp-server@latest"],
        "env": {
          "ENFYRA_API_URL": "http://localhost:3000/api",
          "ENFYRA_API_TOKEN": "efy_pat_your-token"
        }
      }
    }
  }
}

Restart or reload the MCP client after writing configuration. Keep the token out of committed files.

Config Command

npx @enfyra/mcp-server@latest config [options]

| Option | Use | |---|---| | --app-url | Set the Enfyra app/admin URL | | --api-token, -t | Set ENFYRA_API_TOKEN | | --yes | Run non-interactively | | --reconfig | Select clients again and replace the existing enfyra entry | | --compact-tools | Use guided dynamic packs to minimize the initial tool manifest | | --static-tools | Use the guided static manifest instead of dynamic packs | | --codex | Write Codex config | | --claude-code, --claude | Write Claude Code config | | --cursor | Write Cursor config | | --vscode, --copilot | Write VS Code / GitHub Copilot config | | --antigravity | Write Google Antigravity config | | --zcode | Write ZCode config | | -h, --help | Show CLI help |

Environment

| Variable | Description | Default | |---|---|---| | ENFYRA_API_URL | Runtime API base written into MCP config | Required | | ENFYRA_API_TOKEN | Programmatic token from the Enfyra admin UI /me | Required |

The MCP server always uses the guided surface; low-level tools remain hidden. Re-running config preserves existing ENFYRA_MCP_DYNAMIC_TOOLS and ENFYRA_MCP_PROFILE values. Pass --compact-tools or --static-tools only when intentionally changing the tool-loading mode.

The API token is exchanged for a short-lived access token at runtime. It is not sent directly as a Bearer token.

Verify the Connection

Open a new session in the configured MCP client and ask it to:

Use Enfyra MCP to show the connected API context.

Then try a read-only request:

Use Enfyra MCP to list the available tables without changing anything.

Development

This repository uses Yarn 4 and TypeScript:

yarn typecheck
yarn test

Use AGENTS.md for maintainer architecture, tool contracts, verification rules, and backend sync points. LLM runtime guidance is served by the MCP instructions, tool descriptions, workflow discovery, required-knowledge tools, builders, and examples—not by this README.