English Français العربية

Figranium MCP

Official registry Search and web

MCP server for creating, running, inspecting, and scheduling Figranium browser automations.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package figranium-mcp
Claude Code 
claude mcp add figranium-mcp -- npx -y figranium-mcp@1.4.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "figranium-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "figranium-mcp@1.4.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Figranium MCP Server
  2. Use Figranium with MCP
  3. Quick start
  4. What agents can do
  5. Local vs hosted MCP
  6. Environment variables
  7. Build from source
  8. Links

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:

ToolPurpose
task_listDiscover existing Tasks
create_taskCreate a new Task
task_executeExecute a Task with optional variable overrides
execution_listInspect previous executions
schedule_listFind scheduled Tasks
schedule_get_all_statusInspect scheduler state
schedule_get_statusInspect one Task's schedule
schedule_setCreate or update a schedule
schedule_deleteRemove a schedule
schedule_describeValidate and preview a schedule

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.

Environment variables

VariableRequiredDefaultDescription
FIGRANIUM_API_KEYYes—API key generated by your Figranium instance
FIGRANIUM_BASE_URLNohttp://localhost:11345Base URL of the Figranium instance

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

Frequently asked questions

What is Figranium MCP?

MCP server for creating, running, inspecting, and scheduling Figranium browser automations.

How do I install Figranium MCP?

It runs on your machine. In Claude Code: claude mcp add figranium-mcp -- npx -y figranium-mcp@1.4.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Figranium MCP need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Figranium MCP open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Figranium MCP?

It is published by figranium. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.