J
jorgeortega/openapi-agentify
Turn the API you already run into an MCP server: one middleware, from your OpenAPI spec, in-process.
更新 2026-11-12
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · jorgeortega/openapi-agentify · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
jorgeortega/openapi-agentify;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# openapi-agentify
以下摘录自该仓库的 README(片段)
Turn the API you already run into an MCP server: one middleware, from your OpenAPI spec, in-process.
Try it without installing anything: the example Orders API runs in your
browser, and npm run try or npm run inspect (the MCP Inspector) talks to
its /mcp.
Three lines on Express:
ts
import { agentify } from "openapi-agentify/express";
import { defineConfig } from "openapi-agentify";
app.use(agentify(defineConfig({ name: "Acme Orders API", spec: "./openapi.yaml" }))); // first, before body parsers and auth
Add one middleware to your Express, Hono, Fastify or Next.js app. It reads
your OpenAPI spec (or drafts one from your routes) and serves /mcp with one
tool per operation. A tool call becomes the HTTP request the operation
describes and runs in-process through your own routes: your auth
middleware, your validation and your handlers, the ones you already test.
There is no second server, no proxy and no extra port.
It also serves what agents read before they call: llms.txt, an MCP server
card, the AI Catalog, your spec with agent hints, and /agent, an index of
all of them. And it scores how well a model will understand your spec, then
suggests the fixes.
## Quick start (30 seconds)
bash
cd your-api
npx openapi-agentify init --write
npm install
npm run dev
init detects the framework and the file that creates your app, finds your
spec (or drafts one from your routes), scores it, writes agentify.config.ts
and agentify.tools.json (reads on, writes off), and adds two lines to your
entry file. Then point any MCP client at http://localhost:3000/mcp:
bash
npx @modelcontextprotocol/inspector # Streamable HTTP, http://localhost:3000/mcp
Or by hand, on Express: the three lines at the top, in context.
ts
import express from "express";
import { agentify } from "openapi-agentify/express";
import { defineConfig } from "openapi-agentify";
const app = express();
app.use(agentify(defineConfig({ name: "Acme Orders API", spec: "./openapi.yaml" }))); // first, before body parsers and auth
app.use(express.json());
app.get("/v1/orders/:id", requireApiKey, getOrder); // unchanged
## Frameworks
| Framework | Versions | Mount | Tool calls reach your app through |
| Express | 4 and 5 | app.use(agentify(config)) | an in-memory IncomingMessage/ServerResponse pair, through app itself |
| Hono | 4 | app.use(agentify(config, { app })) | app.fetch(request, env), with your bindings |
| Fastify | 5 | await app.register(agentifyFastify, config) | app.inject() |
| Next.js (App Router) | 15 and 16 | agentifyNext(config, { routes }), a catch-all route and wrap() | the route module's exported GET/POST/… |
Need a socket (TLS client certificates) or another language? dispatch:
{ mode: "http", url } sends tool calls over loopback HTTP instead.
## How it fits
npx openapi-agentify init reads package.json, finds or drafts the spec,
scores agent readiness, writes agentify.config.ts
your app (Express · Hono · Fastify · Next.js)
┌───────────────────────────────────────────────────────────────────────┐
│ app.use(agentify(config)) │
│ POST /mcp MCP (2026-07-28 and 2025-xx) │
│ GET /openapi.json, /openapi.yaml your spec, with agent hints │
│ GET /llms.txt, /llms-full.txt for models reading docs │
Try it without installing anything: the example Orders API runs in your
browser, and npm run try or npm run inspect (the MCP Inspector) talks to
its /mcp.
Three lines on Express:
ts
import { agentify } from "openapi-agentify/express";
import { defineConfig } from "openapi-agentify";
app.use(agentify(defineConfig({ name: "Acme Orders API", spec: "./openapi.yaml" }))); // first, before body parsers and auth
Add one middleware to your Express, Hono, Fastify or Next.js app. It reads
your OpenAPI spec (or drafts one from your routes) and serves /mcp with one
tool per operation. A tool call becomes the HTTP request the operation
describes and runs in-process through your own routes: your auth
middleware, your validation and your handlers, the ones you already test.
There is no second server, no proxy and no extra port.
It also serves what agents read before they call: llms.txt, an MCP server
card, the AI Catalog, your spec with agent hints, and /agent, an index of
all of them. And it scores how well a model will understand your spec, then
suggests the fixes.
## Quick start (30 seconds)
bash
cd your-api
npx openapi-agentify init --write
npm install
npm run dev
init detects the framework and the file that creates your app, finds your
spec (or drafts one from your routes), scores it, writes agentify.config.ts
and agentify.tools.json (reads on, writes off), and adds two lines to your
entry file. Then point any MCP client at http://localhost:3000/mcp:
bash
npx @modelcontextprotocol/inspector # Streamable HTTP, http://localhost:3000/mcp
Or by hand, on Express: the three lines at the top, in context.
ts
import express from "express";
import { agentify } from "openapi-agentify/express";
import { defineConfig } from "openapi-agentify";
const app = express();
app.use(agentify(defineConfig({ name: "Acme Orders API", spec: "./openapi.yaml" }))); // first, before body parsers and auth
app.use(express.json());
app.get("/v1/orders/:id", requireApiKey, getOrder); // unchanged
## Frameworks
| Framework | Versions | Mount | Tool calls reach your app through |
| Express | 4 and 5 | app.use(agentify(config)) | an in-memory IncomingMessage/ServerResponse pair, through app itself |
| Hono | 4 | app.use(agentify(config, { app })) | app.fetch(request, env), with your bindings |
| Fastify | 5 | await app.register(agentifyFastify, config) | app.inject() |
| Next.js (App Router) | 15 and 16 | agentifyNext(config, { routes }), a catch-all route and wrap() | the route module's exported GET/POST/… |
Need a socket (TLS client certificates) or another language? dispatch:
{ mode: "http", url } sends tool calls over loopback HTTP instead.
## How it fits
npx openapi-agentify init reads package.json, finds or drafts the spec,
scores agent readiness, writes agentify.config.ts
your app (Express · Hono · Fastify · Next.js)
┌───────────────────────────────────────────────────────────────────────┐
│ app.use(agentify(config)) │
│ POST /mcp MCP (2026-07-28 and 2025-xx) │
│ GET /openapi.json, /openapi.yaml your spec, with agent hints │
│ GET /llms.txt, /llms-full.txt for models reading docs │
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/jorgeortega-openapi-agentify/)
- 来源
- awesome · https://github.com/jorgeortega/openapi-agentify
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。