Actionforge MCP server

ActionForge MCP server

Publishes an ActionForge account's tools to any MCP client — Claude Desktop, Claude Code, or anything else speaking the Model Context Protocol.

ActionForge turns a description and a pair of JSON Schemas into a hosted API endpoint. You describe the function you need; it generates the implementation, deploys it as a serverless function, and returns a validated URL. Every tool is a pure function of its input — generated code is scanned before deploy and refused if it reaches the network or executes code built at runtime.

This package is the MCP bridge: your endpoints become tools Claude can call directly. It has no runtime dependencies — stdio, fetch, and about 500 lines.

Get an API key at pritas.github.io/actionforge_ui.

The mapping is close to one-to-one, which is why this wrapper is thin: an ActionForge tool already is an MCP tool — a name, a description, a JSON Schema for input, and one for output. tools/list reads GET /api/tools; tools/call posts to the tool's proxy URL.

Implemented directly against the 2025-06-18 protocol schema rather than via the SDK. That keeps the install to a single package with nothing beneath it, and every branch stays exercisable offline — npm run smoke drives the compiled server over stdio against a closed port, so the handshake, the silence expected of a notification, and transport-failure handling are all checked without an account.

Install

npx actionforge-mcp

Zero runtime dependencies — the whole server is stdio, fetch, and about 500 lines. Nothing to install beyond Node 20.12+.

From a checkout of this repo instead:

npm install
npm run build
node dist/server.js

Configure

export ACTIONFORGE_URL=https://your-deployment.example.com
export ACTIONFORGE_API_KEY=af_...        # from POST /api/signup, or npm run keygen
npx actionforge-mcp

Everything published is scoped to that key's account. Point it at a different key and it publishes a different tenant's tools — the API enforces the scoping, so the MCP server cannot see past it.

Transport is stdio with newline-delimited JSON. stdout carries protocol frames only; all logging goes to stderr, because anything else corrupts the stream a client is parsing.

Claude Desktop

claudedesktopconfig.json:

{
  "mcpServers": {
    "actionforge": {
      "command": "npx",
      "args": ["-y", "actionforge-mcp"],
      "env": {
        "ACTIONFORGE_URL": "https://your-deployment.example.com",
        "ACTIONFORGE_API_KEY": "af_..."
      }
    }
  }
}

Claude Code

claude mcp add actionforge \
  --env ACTIONFORGE_URL=https://your-deployment.example.com \
  --env ACTIONFORGE_API_KEY=af_... \
  -- npx -y actionforge-mcp

How failures are reported

The protocol draws a line this server follows exactly, because it decides whether a model can recover on its own:

Anything the model could act on stays inside the result where it can see it. Only genuinely exceptional conditions become protocol errors.

Caching

Shortened. The full README is on GitHub.