Figranium MCP

Figranium MCP Server

The official Model Context Protocol (MCP) server for Figranium, built with the official Figranium JavaScript SDK API client.

View

Use Figranium with MCP

Figranium turns website workflows into reusable Tasks that AI agents can discover, create, and run through MCP. This server is the local STDIO client for connecting an MCP-compatible app to your Figranium instance.

Looking for the hosted OAuth MCP instead? Connect compatible remote MCP clients to https://mcp.figranium.dev/mcp.

Quick start

You need a running Figranium instance and an API key from Figranium settings.

Run the MCP server directly from npm:

FIGRANIUM_API_KEY=YOUR_API_KEY npx -y figranium-mcp

By default, it connects to Figranium at http://localhost:11345. To use another instance:

FIGRANIUM_BASE_URL=https://your-figranium-instance.example.com \

FIGRANIUM_API_KEY=YOUR_API_KEY \ npx -y figranium-mcp

MCP client configuration

Most local MCP clients accept a configuration shaped like this:

{

"mcpServers": { "figranium": { "command": "npx", "args": ["-y", "figranium-mcp"], "env": { "FIGRANIUM_BASE_URL": "http://localhost:11345", "FIGRANIUM_API_KEY": "YOUR_API_KEY" } } } }

Use that server entry in clients such as Codex, Claude Code, Cursor, GitHub Copilot, Claude Desktop, Cline, and other STDIO MCP clients.

If the MCP server itself runs inside Docker while Figranium runs on the host, use http://host.docker.internal:11345 instead of http://localhost:11345.

What agents can do

Once connected, an agent can work with Figranium without manually calling its API. The MCP server exposes tools for the core Task lifecycle:

The server also exposes figranium://schemas/task-v1.json, allowing clients to inspect the Figranium Task schema directly.

Figranium's MCP instructions teach agents how to construct Tasks, choose selectors, use variables, and follow Task sequencing rules. Invalid Task payloads return structured validation diagnostics so an agent can correct its own request.

Local vs hosted MCP

The npm package contains the local STDIO MCP server. It does not ship the Figranium MCP landing page or hosted OAuth UI.

For clients that support remote OAuth MCP, use:

https://mcp.figranium.dev/mcp

The hosted MCP handles OAuth and connects the client to a publicly reachable Figranium instance. For local clients, npx -y figranium-mcp is usually the simpler path and can connect directly to localhost.

Authenticated template catalog requests reject HTTP redirects to prevent x-api-key credentials from reaching a redirected destination. Point FIGRANIUM_BASE_URL at the final API origin; do not rely on a reverse proxy's 3xx redirect.

Environment variables

The server exits with a setup message if FIGRANIUM_API_KEY is missing.

Build from source

Requires Node.js 18+ and npm 9+.

git clone https://github.com/figranium/figranium-mcp.git

cd figranium-mcp npm install npm run build

Run the compiled server:

FIGRANIUM_API_KEY=YOUR_API_KEY npm start

For active development:

npm run watch

Run the test suite:

npm test

MCP Inspector

You can inspect the published server with the official MCP Inspector:

FIGRANIUM_API_KEY=YOUR_API_KEY npx @modelcontextprotocol/inspector npx -y figranium-mcp

Links

• Figranium documentation
• Figranium
• npm package
• MCP server source
• Figranium source