@fascia-run/mcp-server

@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

• On startup, fetches your workspace's spec bundle (entities, tools, policies)
• 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
• Registers entity schemas and tool specs as MCP resources
• Polls for bundle updates in the background (configurable interval)
• 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