Frankenclaw MCP Server

FrankenClaw is a minimal framework for building MCP tools. Drop a Python file in `tools/`, write one async function with a docstring, flip it on in

Local serverstdioPython

What is the Frankenclaw MCP server?

If you already use Frankenclaw, the frankenclaw mcp server is the piece that lets your assistant work with it directly. FrankenClaw is a minimal framework for building MCP tools. Drop a Python file in tools/, write one async function with a docstring, flip it on in your config — your agent has a new tool. No server edits, no registration boilerplate, no.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • FrankenTool — What It Does
  • web_scrape — Scrape any page to clean markdown — no ads, no nav
  • search_web — Web search returning title/url/snippet
  • file_find — Find files on this machine from a fuzzy description

Installation

and on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: FIRECRAWL_API_KEY, FRANKENCLAW_KEYS_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Python 3.12+ - A Firecrawl API key for the bundled web_scrape example (or remove it from enabled_tools and add your own tools) The chassis core is just FastMCP. Tools you add bring their own dependencies — install those yourself.

Where it fits

Plenty of search and retrieval servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Frankenclaw's toolset — FrankenTool, web_scrape, search_web and 1 more — is a fair guide to whether it matches your workflow. It is maintained by guymanndude; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
FrankenToolWhat It Does
web_scrapeScrape any page to clean markdown — no ads, no nav
search_webWeb search returning title/url/snippet
file_findFind files on this machine from a fuzzy description

How to install the Frankenclaw MCP server

{
  "mcpServers": {
    "frankenclaw": {
      "command": "uvx",
      "args": ["and"],
      "env": {
        "FIRECRAWL_API_KEY": "your-value",
        "FRANKENCLAW_KEYS_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Python 3.12+ - A Firecrawl API key for the bundled web_scrape example (or remove it from enabled_tools and add your own tools) The chassis core is just FastMCP. Tools you add bring their own dependencies — install those yourself.
VariableDescriptionRequired
FIRECRAWL_API_KEYCredential the server authenticates with.Yes
FRANKENCLAW_KEYS_PATHCredential the server authenticates with.Yes

Example prompts to try

  • Use Frankenclaw to FrankenTool.
  • Use Frankenclaw to web scrape.
  • Use Frankenclaw to search web.

Frequently asked questions

It connects Frankenclaw to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (FrankenTool, web_scrape, search_web, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Frankenclaw directly.