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

@fascia-run/mcp-server

v0.1.1

Published

MCP server for Fascia — expose deployed Tools to AI agents

Downloads

98

Readme

@fascia-run/mcp-server

MCP (Model Context Protocol) server for Fascia - expose your deployed Tools and Entity schemas to AI agents like Claude, Cursor, and other MCP-compatible clients.

What it does

This server connects to your Fascia workspace and exposes:

  • Tools - All HTTP-triggered Tools become callable MCP tools (with risk level annotations)
  • Resources - Entity schemas, Tool specs, and workspace metadata available as MCP resources

Quick start

Install

npm install -g @fascia-run/mcp-server

Configure

Set your Fascia API key as an environment variable:

export FASCIA_API_KEY="your-api-key"

Get your API key from fascia.run/app/settings (API Keys section).

Use with Claude Code

Add via CLI or edit .mcp.json in your project root:

claude mcp add --scope user --transport stdio fascia -- fascia-mcp-server

Or manually add to .mcp.json:

{
  "mcpServers": {
    "fascia": {
      "command": "fascia-mcp-server",
      "env": {
        "FASCIA_API_KEY": "your-api-key"
      }
    }
  }
}

Use with Claude Desktop

Add to your Claude Desktop config:

{
  "mcpServers": {
    "fascia": {
      "command": "npx",
      "args": ["-y", "@fascia-run/mcp-server"],
      "env": {
        "FASCIA_API_KEY": "your-api-key"
      }
    }
  }
}

Use with Cursor

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

{
  "mcpServers": {
    "fascia": {
      "command": "npx",
      "args": ["-y", "@fascia-run/mcp-server"],
      "env": {
        "FASCIA_API_KEY": "your-api-key"
      }
    }
  }
}

Environment variables

| Variable | Required | Default | Description | |----------|----------|---------|-------------| | FASCIA_API_KEY | Yes | - | Your Fascia workspace API key | | FASCIA_API_URL | No | https://api.fascia.run/api/v1 | API base URL | | FASCIA_POLL_INTERVAL_MS | No | 60000 | Bundle refresh interval (ms). Set to 0 to disable. |

How it works

  1. On startup, fetches your workspace's spec bundle (entities, tools, policies)
  2. Registers each HTTP-triggered Tool as an MCP tool with:
    • Input schema derived from the Tool's JSON Schema definition
    • Risk level annotation (Green/Yellow/Red)
    • Read-only, destructive, idempotent, and open-world hints from flow analysis
  3. Registers entity schemas and tool specs as MCP resources
  4. Polls for bundle updates in the background (configurable interval)
  5. Tool calls are forwarded to the Fascia Executor for deterministic execution

MCP capabilities

Tools

Each Fascia Tool with an HTTP trigger is exposed as fascia_{tool_name}. For example, a Tool named createReservation becomes fascia_create_reservation.

Resources

| URI | Description | |-----|-------------| | fascia://workspace/info | Workspace metadata (entity/tool counts, spec version) | | fascia://entities/{name} | Entity schema for a specific entity | | fascia://tools/{name} | Full spec for a specific tool |

License

MIT