
Fabrx
- Typeless-Git/fabrx-mcp-server
Fabrx is an MCP server that helps you build APIs from documents inside your IDE through the Fabrx stdio npm integration.
About
Fabrx MCP is a stdio Model Context Protocol server published as the npm package fabrx that connects the Fabrx document-driven API workflow to agents in Claude Code, Cursor, and similar IDEs. developers often accumulate PRDs, OpenAPI sketches, and README endpoint lists faster than they write Express or Fastify handlers; this server lets the agent read those artifacts and propose or implement API structures aligned with Fabrx’s model. You install via npm at version 1.0.3 and register stdio transport in your MCP config, which keeps latency low for iterative “change the spec, regenerate the routes” loops. It is a task integration, not a full methodology skill: you still own auth, data modeling, and deployment. Pair it with your existing test and review skills before ship. Confidence is moderate where public tool manifests are sparse, but the registry description and package metadata clearly anchor document-to-API generation.
- 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
Fabrx by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add fabrx -- npx -y fabrxAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | fabrx |
|---|---|
| Transport | STDIO |
| Auth | None |
| Repository | Typeless-Git/fabrx-mcp-server ↗ |
What it does
Generate or evolve HTTP APIs from product documents and specs directly inside your IDE via the Fabrx MCP bridge.
Who is it for?
Best when you maintain API specs or product docs and want agent-assisted backend scaffolding from those sources.
Skip if: Skip if you need only frontend components or that already have a frozen OpenAPI with no document iteration.
What you get
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
By the numbers
- Registry version 1.0.3
- npm identifier fabrx with stdio transport
- GitHub repository Typeless-Git/fabrx-mcp-server
Recommended MCP Servers
How it compares
Document-to-API MCP bridge, not a hosted PDF or e-invoice server.
FAQ
Who is Fabrx for?
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.