openapi-agentify
Related Servers
Alternatives to openapi-agentify
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceTurns existing FastAPI routes (or any OpenAPI spec) into owner-approved MCP tools served from one governed endpoint, keeping tools hidden until an owner reviews a diff and enables them. Agents get incremental discovery via meta-tools, response field projection, per-caller API-key policy, PII redaction, and a JSON-lines audit log.160 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceTurns any OpenAPI 3.x spec into an MCP server that exposes one validated tool per API operation, so AI agents can discover and call a REST API over stdio or Streamable HTTP. It is read-only by default, with allow/deny lists, environment-based auth, timeouts and response truncation for safe agent access.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to call existing Node.js API routes as MCP tools across NestJS, Express, Fastify, Koa, Hono, and AdonisJS, preserving existing auth, validation, and middleware.11 npm1MIT
- AlicenseNot gradedqualityAmaintenanceTurns an existing Hono API into an MCP server so AI agents like Claude and Cursor can discover and call its routes as tools. Each route's existing zod validator becomes the tool's input schema, so validation, auth middleware, and logging keep working exactly as they do for HTTP clients.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables building agent-ready APIs that expose tools as both HTTP and MCP endpoints from a single server definition, with automatic OpenAPI, discovery docs, and interactive API reference.5Apache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes Express.js API endpoints as MCP tools, preserving existing schemas and authentication behavior. Supports streaming responses and can be mounted directly to existing Express apps or run as a standalone gateway.11 npm1MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: listOrders discovers and paginates orders, getOrder retrieves one order's details, and getSalesReport aggregates paid-order totals. The descriptions explicitly guide when to use listOrders before getOrder, leaving no meaningful overlap.
All tools follow a predictable camelCase verb+noun pattern: listOrders, getOrder, getSalesReport. The singular/plural noun choices match the operation semantics.
Three tools are a reasonable, well-scoped set for a minimal read-only orders/reporting interface. It is slightly thin, but each tool earns its place and there is no bloat.
The surface covers listing, single-order retrieval, and sales aggregation, but it lacks order creation, status updates, refunds, and deletion. For an Orders API domain, these are notable gaps that would leave agents unable to perform common lifecycle operations.