Figranium MCP

io.github.figraniumPublished by GitHub account figraniumv1.4.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & Workflow Browser Automation

Server details

Identifier: io.github.figranium/figranium-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account figranium for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.figranium%2Ffigranium-mcp.svg)](https://sourceweft.com/mcp/io.github.figranium%2Ffigranium-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local STDIO MCP server that lets an assistant discover, create, run, inspect and schedule Figranium browser-automation Tasks.

What you can do: Discover and create Figranium Tasks, with the Task schema exposed for inspection
Execute Tasks, optionally overriding variables, and review past executions
List, create, update, delete and preview schedules, and check scheduler state
Receive structured validation diagnostics for invalid Task payloads so requests can be corrected
When to use it: Use it when you already run a Figranium instance and want an MCP-capable assistant to build and operate website automation Tasks and their schedules without calling the Figranium API by hand.
Requirements: Runs locally via npx with Node.js; needs a running Figranium instance and an API key in FIGRANIUM_API_KEY. FIGRANIUM_BASE_URL optionally points at a non-default instance (default Desktop-only; no remote endpoint in this package.

Before you install

The API key in FIGRANIUM_API_KEY grants access to your Figranium instance, so keep it out of shared configs. The server can create Tasks, execute them, and create, update or delete schedules, which changes state on the instance. Authenticated requests reject redirects; point FIGRANIUM_BASE_URL at the final API origin rather than a proxy that redirects.

Installation

In SourceWeft

Open Figranium MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Figranium Banner]

Figranium MCP Server

[NPM] [Glama quality and maintenance score]
[Listed on MCP Market]

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:

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

bash

FIGRANIUM_BASE_URL=https://your-figranium-instance.example.com \FIGRANIUM_API_KEY=YOUR_API_KEY \npx -y figranium-mcp

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:

json

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

{  "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:

Tool	Purpose
`task_list`	Discover existing Tasks
`create_task`	Create a new Task
`task_execute`	Execute a Task with optional variable overrides
`execution_list`	Inspect previous executions
`schedule_list`	Find scheduled Tasks
`schedule_get_all_status`	Inspect scheduler state
`schedule_get_status`	Inspect one Task's schedule
`schedule_set`	Create or update a schedule
`schedule_delete`	Remove a schedule
`schedule_describe`	Validate 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:

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+.

Run the compiled server:

For active development:

Run the test suite:

MCP Inspector

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

Links

Source: README.md at commit 7f156c1

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.4.0LatestOct 10, 2026
v1.3.3Sep 23, 2026
v1.2.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Variable	Required	Default	Description
`FIGRANIUM_API_KEY`	Yes	—	API key generated by your Figranium instance
`FIGRANIUM_BASE_URL`	No	`http://localhost:11345`	Base URL of the Figranium instance