MCP Factory

Name: MCP Factory
Author: jaimenbell

by jaimenbellversion 0.1.3i★ –iRuns on your computer

Registry nameio.github.jaimenbell/mcp-factory

Install

Overview

Description from the maker (original English)

Manifest-driven MCP server scaffolder and runtime hub for tool integrations.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 24/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "factory": {
      "command": "uvx",
      "args": [
        "jaimenbell-mcp-factory"
      ]
    }
  }
}

Run this in your terminal

claude mcp add factory -- uvx jaimenbell-mcp-factory

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "factory": {
      "command": "uvx",
      "args": [
        "jaimenbell-mcp-factory"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "factory": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "jaimenbell-mcp-factory"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account jaimenbell, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 19062 servers in this category
Published to the registry more recently than 22% of the other 19062 servers in this category
Basic checks equal to or better than 100% of the other 19062 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Factory safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Agent Guild

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated yesterday

Runs in the cloud✓ desktopcommander.app

Install

Agent Guild

Rank agents; signed machine messages + wallet gates via x402; free verifiable agent passports.

by AgentTanukiEarlyUpdated today

Runs in the cloud

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MCP Factory

*The test count is verifiable below (python -m pytest tests/ → 348 passed, 8 skipped) and enforced in CI by scripts/check_readme_counts.py, which fails the build if this README's counts drift from the live suite.*

60-Second Quickstart

From PyPI (registry users):

pip install jaimenbell-mcp-factory

mcp-factory-hub --serve

equivalent: python -m mcp_factory --serve

From a git checkout (contributors): see the python hub_server.py ... examples throughout this README — hub_server.py at the repo root is a backward-compat wrapper around the same mcp_factory.cli module the console script runs, so behavior is identical either way.

The manifest-driven engine behind the MCP Integration Sprint. Write one mcp.yaml for a bot repo and the factory generates the server stub and the ~/.claude.json entry; run the hub and it serves every bot's tools through a single MCP endpoint.

The SDK wrapper is the easy part. What makes an MCP server safe to put in front of a real internal tool — scoped auth/env, fail-soft error handling, validated manifests, a collision-safe registry, and a real test suite — is the engineering this engine is built around. That same production layer is hand-built per engagement; the factory scaffolds it, it doesn't fake it.

Browse before you reply

This repo is public so you can verify the discipline instead of taking my word for it. Every claim below maps to a file you can open:

Claim	Where it lives	What to look for
Validated, env-scoped manifests	`mcp_factory/manifest.py`	strict `from_dict` validation (raises on missing/invalid fields); the `env_required` / `env` model that scopes which secrets a server may see
Fail-soft subprocess proxying	`mcp_factory/runtime/subprocess_adapter.py`	typed `SubprocessError`, lazy start, JSON-RPC error surfacing, `timeout`/`OSError`-guarded teardown + `atexit` cleanup — a dead bot returns a clean error, it doesn't crash the hub
Collision-safe, manifest-driven registry	`mcp_factory/runtime/registry.py` · `registry.json`	`CollisionError` on duplicate `.` names; the registry is built from manifests, not hand-maintained
Tested on a clean checkout	`tests/`	348 passed, 8 skipped, 0 failed (Python 3.12); the 8 skips are real integration tests or lint checks that no-op when the thing they need is absent

Honesty rails: 348 is the real, reproducible count on a clean checkout — the same number the public CI run produces and gates on. mcp-factory generates the *scaffold* and runs the hub — it does not "generate the production server" or carry any client/CI claims. The hardened production layer (per-tool auth boundaries, the full failure set, two-axis version-pinning) is built per engagement on top of this engine. That applies to both Python scaffold styles below — see "Two Python styles" for exactly what the fastmcp variant does and doesn't add on top of that baseline.

Quick Start

Factory mode (generate config from one manifest)

# Reference an existing MCP server (no code generated — just the config entry)

python hub_server.py --manifest examples/fleet_health.yaml

Scaffold a new MCP server from scratch

python hub_server.py --manifest my_bot/mcp.yaml --output-dir my_bot/

Dry run — preview without writing

python hub_server.py --manifest my_bot/mcp.yaml --dry-run

Self-verify: compare factory output to live ~/.claude.json entry

python hub_server.py --manifest examples/fleet_health.yaml --verify ~/.claude.json

Output always goes to ~/.claude.json.factory-test by default — never to the live ~/.claude.json. Copy entries manually after review.

Scan mode (batch-register all bots)

# Dry-run diff: show what would change in ~/.claude.json

python hub_server.py --scan C:\path\to\projects

Apply: write ~/.claude.json after backing it up

python hub_server.py --scan C:\path\to\projects --apply

Force-update entries already registered

python hub_server.py --scan C:\path\to\projects --apply --force

--scan discovers all projects/*/mcp.yaml files, validates each, and diffs them against the current ~/.claude.json. Default root is C:\path\to\projects. With --apply, a timestamped backup is created at ~/.claude.json.scan-backup- before writing.

Skip logic: manifests whose name already exists in ~/.claude.json are skipped unless --force is passed. This prevents accidentally overwriting manually-crafted entries.

Serve mode (runtime hub — single MCP for all bots)

# Run the hub as a live MCP server (stdio transport)

python hub_server.py --serve

Serve with multiple scan roots (repeatable)

python hub_server.py --serve \ --scan-root C:\path\to\projects \ --scan-root C:\path\to\Claude

Register+serve in one step (scan --apply then start hub)

python hub_server.py --register \ --scan-root C:\path\to\projects \ --scan-root C:\path\to\Claude

The hub scans all mcp.yaml manifests under each --scan-root at startup, then exposes every bot's tools under the . namespace (e.g., fleet-health.fleet_status, my-bot.run_scan). Tools are proxied to per-bot subprocess MCP servers with lazy startup.

Hub meta-tool: _hub.list_bots returns the registered bots and their subprocess status.

Hub is pre-registered in ~/.claude.json as mcp-factory-hub (see scripts/register_hub.py).

Node.js template

Factory generates Node.js stubs when runtime.type: node is set in mcp.yaml:

runtime:

type: node command: "node" output: "path/to/server.js"

Generated stubs use @modelcontextprotocol/sdk with stdio transport and zod for argument validation. See examples/node_example.yaml for a working demo.

Two Python styles: raw SDK vs. FastMCP

For runtime.type: python, the factory can scaffold either of two styles from the exact same manifest:

runtime:

type: python command: "python" style: raw # default — official mcp SDK, hand-rolled list_tools/call_tool

style: fastmcp # FastMCP v3 (PrefectHQ/fastmcp), decorator-based tool registration

Both styles read the same tools: / env_required: fields and produce a server that speaks the same stdio JSON-RPC wire protocol — the runtime hub's SubprocessAdapter proxies either one without any adapter changes (see tests/test_fastmcp_template.py::TestFastmcpServeSmoke for a live generate-and-call test).

	`style: raw` (`python_server.py.j2`)	`style: fastmcp` (`python_fastmcp.j2`)
SDK	official `mcp` package, `mcp.server.Server`	`fastmcp` (pinned exact `fastmcp==3.4.2` — 4.0.0b1 is a beta that breaks sampling/roots, do not float)
Tool registration	manual `@server.list_tools()` / `@server.call_tool()` dispatch	one `@mcp.tool(...)`-decorated function per tool
Arg schema	hand-built JSON Schema dict per arg	`Annotated[type, Field(description=...)]` on real Python parameters — FastMCP derives the JSON Schema, including required/optional, from the signature
Tool body	`# TODO: implement` stub	same stub, wrapped in `try/except Exception` — a runtime error in a filled-in implementation returns a structured `{"status": "error", ...}` instead of crashing the process
`env_required`	not enforced at scaffold level	rendered into a `_check_required_env()` startup check that warns to stderr if a declared var is missing — a presence check, not credential validation

Gaps, stated honestly: neither style implements per-tool authorization, rate limiting, or the "full failure set" the hub-level subprocess_adapter.py gives you for free (typed errors, lazy start, atexit cleanup) — that's still a per-engagement build on top of either scaffold. The fastmcp template's fail-soft wrapper and env-presence check are new, real code (read mcp_factory/templates/python_fastmcp.j2), not a marketing claim about auth — they were added because FastMCP's decorator model made them cheap to include cleanly; they have not (yet) been backported to the raw template, which is why the two styles differ slightly in what ships out of the box. If your engagement needs FastMCP-specific features beyond this (resources, prompts, HTTP/SSE transport, middleware-based auth), the generated file is a normal FastMCP app — extend it directly.

See examples/fastmcp_example.yaml for a working demo manifest.

mcp.yaml Schema

name: my-bot                   # REQUIRED — unique MCP server name (key in claude.json)

description: > # REQUIRED — shown in Claude's tool descriptions What this bot does and when to use it.

runtime: # REQUIRED type: python # python | node | binary command: "C:\\Python314\\python.exe" # full path to interpreter script: "path/to/server.py" # existing server (skips scaffold generation) output: "path/to/out.py" # where to write generated scaffold (omit = auto) style: raw # python only: raw (default) | fastmcp — see "Two Python styles"

tools: # REQUIRED — list of MCP tools to expose

name: tool_name # REQUIRED — programmatic identifier title: "Tool Name" # Optional — human display name (see below) description: > # REQUIRED — used by Claude for routing What this tool does. annotations: # Optional — the four MCP behaviour hints readOnlyHint: true # tool does not modify anything destructiveHint: false # tool does not perform destructive updates idempotentHint: true # repeat calls have no additional effect openWorldHint: false # tool does not touch an open external world args: # Optional list of arguments
name: arg_name # REQUIRED type: string # string | number | boolean | object | array required: true # default: true description: "..." # shown in Claude's tool schema

env_required: # env var names that must be set at runtime

MY_API_KEY

env: # static env vars injected into claude.json entry MY_API_KEY: "" # leave value empty — fill in ~/.claude.json manually

tags: [trading, health] # for documentation / future routing priority: high # high | medium | low

Key rules

runtime.script + existing file → factory references it, skips scaffold
runtime.script + missing file → validation error (use runtime.output for new scaffolds)
runtime.output → explicit path for generated stub (absolute recommended)
Neither script nor output → error at config-write step

`title` and `annotations`

Both are optional and both are worth declaring.

title is the human display name, which lets name stay a programmatic identifier. Display precedence is title → annotations.title → name; the factory exposes only the top-level title so one manifest cannot declare two competing display names.

annotations matters more than it looks. The four hints have pessimistic defaults — destructiveHint and openWorldHint both default to true, readOnlyHint to false —

Only the beginning is shown; read the rest in the repo

MCP Factory

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Agent Guild

README from the maker

MCP Factory

60-Second Quickstart

equivalent: python -m mcp_factory --serve

Browse before you reply

Quick Start

Factory mode (generate config from one manifest)

Scaffold a new MCP server from scratch

Dry run — preview without writing

Self-verify: compare factory output to live ~/.claude.json entry

Scan mode (batch-register all bots)

Apply: write ~/.claude.json after backing it up

Force-update entries already registered

Serve mode (runtime hub — single MCP for all bots)

Serve with multiple scan roots (repeatable)

Register+serve in one step (scan --apply then start hub)

Node.js template

Two Python styles: raw SDK vs. FastMCP

style: fastmcp # FastMCP v3 (PrefectHQ/fastmcp), decorator-based tool registration

mcp.yaml Schema

Key rules

title and annotations

`title` and `annotations`