"openapi" matching MCP servers:

A template for building MCP servers with a built-in paywall gate that offers free local execution and premium server-side execution via Stripe and x402 payment lanes.

MCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.

Turns 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.

Turns any OpenAPI 3.0/3.1 spec into validated MCP tools, letting hosts call allowed API operations locally with strict schemas, secure credential handling, and read-only-by-default filtering.

Enables AI agents to discover, search, and call any REST API described by an OpenAPI or Swagger document. Supports multiple API endpoints with authentication and parameter handling.

Enables efficient exploration of OpenAPI specs via markdown, with progressive disclosure of endpoints, schemas, and batch operations to minimize AI context usage.

Turn any OpenAPI spec into MCP tools for Claude — instantly. Point mcp-openapi at any OpenAPI 3.x spec and Claude can call every endpoint through natural language. No custom integration code. No manual tool definitions. One line of config.

Enables AI agents to explore any OpenAPI 3 spec, inspect endpoints and schemas, generate TypeScript types, and make authenticated API calls using credentials mapped to the spec's security schemes.

An MCP server that crawls and parses OpenAPI JSON or Swagger UI URLs to provide concise endpoint summaries. It enables LLMs to discover and interact with API interfaces by extracting methods, paths, and operation IDs from documentation sources.

Mount any OpenAPI spec as an MCP server, supporting multiple APIs with authentication and resource auto-promotion.

MCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resources for client-side exploration.

A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.

Provides a ready-to-run MCP server and Python SDK for securely interacting with Openapi.com APIs, enabling businesses to retrieve official documents and data through natural language.

Auto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.

Converts OpenAPI documents into MCP services with generated tools, prompts, and resources, supporting HTTP and STDIO transports plus an admin Web UI.

Exposes REST API endpoints defined by OpenAPI specifications as MCP tools, enabling LLMs to discover and interact with those APIs through MCP.

Enables coding agents to check requests against a live OpenAPI 3.x specification rather than guessing, by resolving endpoints from a docs anchor, operationId, path fragment or tag, revealing what each operation accepts and returns with $refs resolved, and diffing a concrete payload to report missing, unknown, mistyped, or forbidden fields with suggested corrections. All five tools are strictly read-only, never touching the API the schema describes, and return actionable errors with close-match suggestions.

A MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context

A minimal MCP server that auto-generates tools from your OpenAPI spec, optimized for Vercel.

Introspects a Django REST API's OpenAPI schema and exposes each endpoint as an MCP tool, enabling Claude or any MCP client to interact with the API via natural language.