Factory MCP server
Manifest-driven MCP server scaffolder and runtime hub for tool integrations.
0 stars
Reviews
Write oneNobody has reviewed Factory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Factory tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it
- Code scan17 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 24 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Factory compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,273 servers
Install Factory in Claude Code, Cursor or VS Code
claude mcp add mcp-factory -- uvx jaimenbell-mcp-factory
What the publisher says
From the Factory repository's README, as published. We do not edit it. Read it on GitHub
MCP Factory
The test count is verifiable below (python -m pytest tests/ → 348 passed, 8 skipped) and enforced in CI by scripts/checkreadmecounts.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 --serveFrom a git checkout (contributors): see the python hubserver.py ... examples throughout this README — hubserver.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:
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.yamlShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Factory: common questions
- Is Factory MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Factory safety report
- How do I install Factory?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Factory need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Factory maintained?
- The last commit was 64 days ago (2026-08-30). The latest release is v0.1.3.