Fabrx
Generate or evolve HTTP APIs from product documents and specs directly inside your IDE via the Fabrx MCP bridge.
Overview
Fabrx is an MCP server for the Build phase that helps you build APIs from documents inside your IDE through the Fabrx stdio npm integration.
What is this MCP server?
- Fabrx MCP npm package fabrx (stdio transport, registry version 1.0.3)
- Stated purpose: build APIs from documents in your IDE
- Open-source server at Typeless-Git/fabrx-mcp-server on GitHub
- Local stdio package—no remote URL in registry entry
- npm identifier fabrx with stdio transport
- GitHub repository Typeless-Git/fabrx-mcp-server
What problem does it solve?
Specs and API ideas sit in markdown while backend routes lag because context-switching between docs and code is slow.
Who is it for?
Indie builders who maintain API specs or product docs and want agent-assisted backend scaffolding from those sources.
Skip if: Teams that need only frontend components or that already have a frozen OpenAPI with no document iteration.
What do I get? / Deliverables
Your agent uses Fabrx MCP to translate document definitions into API work you can refine and ship in the same repo.
- API structure or implementation derived from your documents
- Faster alignment between written specs and backend code in the repo
Recommended MCP Servers
Journey fit
How it compares
Document-to-API MCP bridge, not a hosted PDF or e-invoice server.
Common Questions / FAQ
Who is Fabrx for?
Solo developers and small teams using Fabrx-style document inputs who want MCP-driven API generation in the IDE.
When should I use Fabrx?
Use it during backend build when you have requirements or API docs and need to materialize endpoints without manually transcribing every route.
How do I add Fabrx to my agent?
Install npm package fabrx at version 1.0.3 and add an MCP server entry with stdio transport pointing at that package per your client’s instructions.