This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
AgentBack - AI native API/MCP framework
Empower AI coding agents to build APIs and MCP servers
AgentBack is an ESM/Zod/MCP fork of LoopBack 4 for building HTTP APIs and MCP servers from one codebase. Define a Zod schema once on a decorator and it becomes your request validation, OpenAPI 3.1 spec, MCP tool, and a codegen-free typed client — all from the same DI container. AI coding agents get a real contract to build against, so they can't drift into a second source of truth or a mismatched endpoint. Best practice becomes the path of least resistance. On npm today.
AgentBack is a TypeScript framework for backends whose first reader is an agent, not a human.
Modern services aren't consumed only by web and mobile apps anymore — they're consumed by AI agents that discover tools, inspect schemas, call APIs, retry failures, and chain them into longer workflows. That raises the stakes on drift: a stale OpenAPI doc or tool manifest used to be a documentation bug; for an agent it's a runtime bug — it picks the wrong tool, sends the wrong body, misses an auth requirement, or trusts a response shape that's gone.
So AgentBack bets everything on one Zod schema per operation. To an agent that schema is three things at once: knowledge (the contract is the only documentation a model reliably reads), a constraint (a validated boundary stops a hallucinated argument before it reaches your handler), and a contract (stable, diffable, testable). Define it once and it becomes your REST validation, OpenAPI 3.1, the MCP tool definition, a codegen-free typed client, your tests, and agent-readable surfaces like /llms.txt — served by default, never out of sync.
Two things I cared about getting right:
• Tools are not endpoints. A route never becomes an MCP tool by accident — exposing one is opt-in, so you ship the 3 outcome-level operations an agent actually needs instead of auto-generating 80 CRUD tools that blow the model's context budget.
• Errors agents can fix. Failures come back as a structured envelope a model can read and correct against, not an opaque 500.
Schema-first lost to code-first once, because rigorous schemas were tedious and we're all a little lazy. The economics flipped: agents are tireless, so when the agent writes and maintains the schema the cost of rigor drops to near zero while its value goes up.
It's a refresh of LoopBack (which I co-created 13 years ago) for the agent era, on the DI core I know best. Alpha, on npm today: npm create agentback my-service. Would love feedback from anyone building agent-facing APIs or MCP servers.
Or run: npm create agentback my-service — to scaffold your own in seconds.
Quick update since launch day — a lot has shipped:
• MCP Apps (SEP-1865): a tool can declare a ui: option that links a ui:// widget conformant hosts (Claude Desktop, Goose, VS Code) render inline for the tool's result — interactive UI straight from a tool call.
• First-class file uploads/downloads: declare a fileField() in a route's body schema and one line drives the whole chain — multipart parsing (streamed to a FileStore under a server-generated key, so no client-controlled paths), OpenAPI format: binary emission, and streaming downloads. In-memory, filesystem, and S3 adapters included.
• Session/user-scoped MCP over Streamable HTTP — each session can get its own DI-scoped server, so per-user tool surfaces.
• Front-mounted middleware chain + configurable body parsing (CORS, rate-limiting, JSON/urlencoded/text/raw on one group model).
• Now on Express 5.
Still alpha, still one schema -> every boundary. Repo + docs: github.com/ninemindai/agentback — feedback very welcome.
About AgentBack - AI native API/MCP framework on Product Hunt
“Empower AI coding agents to build APIs and MCP servers”
AgentBack - AI native API/MCP framework was submitted on Product Hunt and earned 6 upvotes and 3 comments, placing #117 on the daily leaderboard. AgentBack is an ESM/Zod/MCP fork of LoopBack 4 for building HTTP APIs and MCP servers from one codebase. Define a Zod schema once on a decorator and it becomes your request validation, OpenAPI 3.1 spec, MCP tool, and a codegen-free typed client — all from the same DI container. AI coding agents get a real contract to build against, so they can't drift into a second source of truth or a mismatched endpoint. Best practice becomes the path of least resistance. On npm today.
AgentBack - AI native API/MCP framework was featured in API (98.4k followers), Open Source (68.6k followers), Artificial Intelligence (473.1k followers), GitHub (41.3k followers) and Vercel Day (20 followers) on Product Hunt. Together, these topics include over 154.7k products, making this a competitive space to launch in.
Who hunted AgentBack - AI native API/MCP framework?
AgentBack - AI native API/MCP framework was hunted by Raymond Feng. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how AgentBack - AI native API/MCP framework stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Raymond Feng
Hey Product Hunt 👋
AgentBack is a TypeScript framework for backends whose first reader is an agent, not a human.
Modern services aren't consumed only by web and mobile apps anymore — they're consumed by AI agents that discover tools, inspect schemas, call APIs, retry failures, and chain them into longer workflows. That raises the stakes on drift: a stale OpenAPI doc or tool manifest used to be a documentation bug; for an agent it's a runtime bug — it picks the wrong tool, sends the wrong body, misses an auth requirement, or trusts a response shape that's gone.
So AgentBack bets everything on one Zod schema per operation. To an agent that schema is three things at once: knowledge (the contract is the only documentation a model reliably reads), a constraint (a validated boundary stops a hallucinated argument before it reaches your handler), and a contract (stable, diffable, testable). Define it once and it becomes your REST validation, OpenAPI 3.1, the MCP tool definition, a codegen-free typed client, your tests, and agent-readable surfaces like /llms.txt — served by default, never out of sync.
Two things I cared about getting right:
• Tools are not endpoints. A route never becomes an MCP tool by accident — exposing one is opt-in, so you ship the 3 outcome-level operations an agent actually needs instead of auto-generating 80 CRUD tools that blow the model's context budget.
• Errors agents can fix. Failures come back as a structured envelope a model can read and correct against, not an opaque 500.
Schema-first lost to code-first once, because rigorous schemas were tedious and we're all a little lazy. The economics flipped: agents are tireless, so when the agent writes and maintains the schema the cost of rigor drops to near zero while its value goes up.
It's a refresh of LoopBack (which I co-created 13 years ago) for the agent era, on the DI core I know best. Alpha, on npm today: npm create agentback my-service. Would love feedback from anyone building agent-facing APIs or MCP servers.