"A guide to getting UK weather forecasts without API keys" matching MCP servers:

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

Converts any REST API endpoints into MCP tools, enabling AI clients like Cursor and Claude Desktop to call internal services directly.

A tool that creates MCP (Model Context Protocol) servers from OpenAPI/Swagger specifications, enabling AI assistants to interact with your APIs.

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.

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

A standalone proxy that transforms any OpenAPI or Swagger-described REST API into an MCP server by mapping API operations to executable MCP tools. It enables AI clients to interact with existing web services through automated HTTP requests based on their official documentation.

Converts any OpenAPI 3.x spec into a live MCP server, making every endpoint a validated tool that AI agents can call without writing glue code.

A TypeScript-based MCP server that enables testing of REST APIs through Cline. This tool allows you to test and interact with any REST API endpoints directly from your development environment.

Turns an OpenAPI spec into a ready-to-run test harness with local LLM agents: WireMock stubs, contract tests, robustness probes, and chaos scenarios you can switch on and off in a running WireMock.

A lightweight, local-first MCP server for executing HTTP requests and managing API collections and environments without cloud dependencies. It enables testing APIs, handling authentication, and importing OpenAPI specifications directly within MCP-compatible workflows.

Converts REST API code (like NestJS controllers or FastAPI endpoints) to Postman collections and environments, helping developers automatically sync their API endpoints with Postman.

Enables AI agents to execute HTTP/REST/GraphQL requests against any endpoint, including private VPN hosts and local services, while logging untruncated headers, request bodies, and raw responses into a local SQLite audit history. Agents can then search that history by keyword, date, method, or status, retrieve full details by ID, and export everything to JSON.

Enables validating API responses against expected schemas/JSON and listing OpenAPI endpoints to enforce API contracts between services.

Enables AI assistants like Claude to interact with any REST API through typed, validated MCP tools. Provides a pattern to wrap REST APIs as MCP servers.

A Model Context Protocol server that creates tools from API configurations defined in YAML files, allowing easy integration of external APIs into an MCP ecosystem without coding.

MCP server that fetches API responses and generates ready-to-use model/POJO classes in your configured language, with built-in login/refresh token handling.

Enables interaction with Nullplatform's API endpoints for managing deployments, scopes, services, and other cloud resources through natural language using the official OpenAPI specification.

Exposes REST API endpoints defined in an OpenAPI Specification as MCP tools, allowing AI models to call them via the ModelContext Protocol.

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.

Enables agents to invoke any REST or SOAP service by sending a normalized payload, with support for API key, Basic, Bearer, and OAuth2 auth. Connectors can be registered once and reused by name.

A bridge that enables any LLM to access and interact with documented REST APIs through the Model Context Protocol (MCP).

Converts SOAP WSDL services into a REST interface and provides MCP tools to describe, invoke, and manage SOAP operations with caching and WS-Security support.

Enables AI clients to exercise a REST API over stdio through a single http_request tool that supports every HTTP method, path/query parameter binding, environment-based auth and global headers, proxy and SSL options, and response size limits. Returned results include status, headers, body and timing, with credentials masked throughout.

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

Enables natural-language chat-driven API testing, letting users upload API specs, run deterministic pytest checks against live targets, inspect results, create defects, and view failure trends.

Enables MCP clients to expose selected operations from local OpenAPI 3.0/3.1 documents as tools, with stdio serving or generated standalone server projects and read-only defaults.

Automatically converts Swagger/OpenAPI specifications into dynamic MCP tools, enabling interaction with any REST API through natural language by loading specs from local files or URLs.

Enables LLMs to make arbitrary HTTP API requests with any method and full control over headers, query parameters, and body.

Enables read-only exploration of YApi projects, categories, and interface docs, and deterministic TypeScript/JavaScript API request function and type generation through a preview-then-apply workflow.

Starter scaffold for a workshop to build an MCP API testing server, intended to be extended through incremental steps.