
Mcp Tool Factory
Spin up new MCP servers from a plain-English brief, an OpenAPI document, or a database schema without writing boilerplate by hand.
Overview
MCP Tool Factory is an MCP server for the Build phase that generates new MCP servers from natural language, OpenAPI, or database schemas using an LLM provider key.
What is this MCP server?
- npm @heshamfsalama/mcp-tool-factory v0.1.0 with stdio MCP transport.
- Generation inputs: natural language, OpenAPI specs, or database schemas.
- Requires one provider key: ANTHROPIC_API_KEY, CLAUDE_CODE_OAUTH_TOKEN, OPENAI_API_KEY, or GOOGLE_API_KEY.
- GitHub: HeshamFS/mcp-tool-factory-ts for templates and workflow details.
- Meta-tooling MCP—produces other MCP servers rather than calling a single SaaS API.
- Package version 0.1.0
- 4 supported LLM credential options (one required)
- Transport: stdio via npm scope @heshamfsalama/mcp-tool-factory
What problem does it solve?
Hand-rolling MCP tool boilerplate for every OpenAPI or database-backed side project burns solo-builder time before the agent can do useful work.
Who is it for?
Indie developers who frequently expose private APIs or SQL-backed admin tools to coding agents and want codegen-assisted MCP setup.
Skip if: Teams that need production-hardened, audited integrations with zero LLM-generated code review, or users without any supported LLM API key.
What do I get? / Deliverables
You get generated MCP server scaffolding from specs or prompts so your agent can call your APIs sooner, with review before ship.
- Generated MCP server project or tool definitions from NL, OpenAPI, or DB schema
- Faster agent-ready wrappers around your APIs
- Repeatable pattern for standing up new MCP integrations on side projects
Recommended MCP Servers
Journey fit
Generating agent tools is core Build work—it accelerates how fast a solo builder exposes proprietary APIs to Claude Code and peers. The factory sits under agent-tooling because its output is MCP servers and tool definitions, not end-user UI.
How it compares
LLM-powered MCP generator, not a finished domain integration like Stripe or Postgres MCP.
Common Questions / FAQ
Who is MCP Tool Factory for?
Solo builders and small teams who know what API or schema they need but want automated MCP server scaffolding inside their agent workflow.
When should I use MCP Tool Factory?
Use it early in build when adding agent-tooling—especially when you have OpenAPI or a DB schema ready and no MCP wrapper yet.
How do I add MCP Tool Factory to my agent?
Install @heshamfsalama/mcp-tool-factory via npm, configure stdio in your MCP client, and set one of ANTHROPIC_API_KEY, CLAUDE_CODE_OAUTH_TOKEN, OPENAI_API_KEY, or GOOGLE_API_KEY.