"Construct 3" matching MCP servers:

Parses Swagger 2.0 and OpenAPI 3.x specifications, exposing API endpoints, schemas, and authentication through MCP tools with local caching to reduce token usage.

Enables local analysis of OpenAPI 3 and Swagger 2 JSON/YAML spec files on disk, with no remote fetching of specs or credentials. It groups endpoints by tag, flags operations that appear to lack security, lists deprecated operations, and produces short markdown cheat sheets for agents.

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.

MCP server for API test case generation from Swagger/OpenAPI specs. Parses Swagger 2.0 and OpenAPI 3.x, generates test cases across 8 categories (positive, negative, boundary, auth, security, idempotency, pagination, business logic), and exports to Postman, TestRail, Allure, k6, pytest, Gherkin, and CSV. Supports internal corporate APIs with auth headers. Auto-saves export files to your working di

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.

Enables Claude Code to interact with any GraphQL API by introspecting the schema and exposing queries and mutations as individual callable tools.

Automatically converts Postman API collections into MCP-compatible tools for AI assistants. Enables users to interact with any API through natural language by generating JavaScript tools from Postman requests.

Gorgon Scout is a Windows web-application and API security scanner (DAST). This connector exposes it as MCP tools, so your AI assistant can record a target you are authorised to test, run the scan, stream findings, and produce a report. Capture needs no proxy or certificate setup, and it intercepts HTTP/1.1, HTTP/2, and HTTP/3 (QUIC). Works with the free Claude Desktop plan.

Generates standalone, human-readable MCP servers from RAML 1.0 or OpenAPI 3.x specs, exposing one tool per resource and method that makes real HTTP calls. It understands Mule/Anypoint auth patterns such as Client ID enforcement and OAuth2, wiring the expected credentials from environment variables at call time.

Provides AI assistants with access to OpenAPI specifications, enabling API discovery, schema retrieval, and direct API execution with support for OAuth 2.0 and other authentication methods.

MCP server to debug Telegram bots by controlling your Telegram user session over MTProto. It enables sending messages, reading chats, handling updates, and invoking raw Telegram API methods.

Exposes Bruno CLI as tools for AI agents, allowing them to discover, inspect, and execute Bruno API collections through the MCP protocol.

Compiles OpenAPI 3.x documents and HTTP manifests into verified MCP tools, serving only operator-approved HTTP operations over Model Context Protocol stdio.

This local stdio MCP server enables AI clients to search, read, and safely write Omeka S REST API resources such as items, media, item sets, site pages and blocks, with value annotations and read-back verification of writes.

Point it at an OpenAPI 3.x document and get an MCP server that exposes the API's endpoints as typed, validated tools for Claude or any MCP client.

Enables interaction with Qonto's Business API for banking operations. Supports all API key-accessible endpoints for managing business banking transactions and account information.

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.

Dynamically generates Model Context Protocol tools, resources, and prompts from OpenAPI 3.x specifications so LLMs can discover and invoke REST API operations through natural language. Supports multiple combined specs, tag-based filtering, enriched tool descriptions, and Basic, Bearer, API key, or Cognito authentication.

HTTP-4-MCP configuration tool allows you to easily convert HTTP API into MCP tool, writing the code written. Through simple interface operation, you can quickly configure an mcp-server.

Runtime MCP server that dynamically bridges any OpenAPI 3.x spec to MCP tools.