"How to obtain an API key" matching MCP servers:

An MCP server that generates MCP servers. Give it an API definition - OpenAPI 3.0/3.1 or a Postman collection or extend an existing server - and it scaffolds a complete, runnable, ownable TypeScript or Python MCP server for that collection of APIs.

An MCP server that makes backend API requests and packages request+response pairs as evidence to prove an endpoint works.

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.

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

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.

API Tester AI - MCP server providing AI-powered tools and automation by MEOK AI Labs

A standalone Model Context Protocol server that enables AI models to access the Australian Pharmaceutical Benefits Scheme (PBS) API data, including medicine listings, pricing, and availability information.

Provides access to Ics Ap Apis API endpoints with authentication support, enabling API interactions through the MCP protocol.

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

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

MCP server enabling AI agents to interact with the Kobra API through authenticated HTTP requests, including partner, bearer, and session auth.

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.

Enables testing and interacting with any REST API endpoint directly from MCP clients like Claude and Cline. Supports GET, POST, PUT, DELETE, and PATCH requests with configurable authentication (Basic, Bearer, API Key), custom headers, SSL verification control, and response size limits.

Enables AI assistants to interact with Magic-API development environment, supporting script syntax query, API management, debugging, and knowledge search for efficient development.

Enables testing and interacting with any REST API endpoints directly from MCP clients such as Claude and Cline, supporting GET, POST, PUT, DELETE, and PATCH requests with detailed status, header, and body responses. It handles Basic, Bearer, and API Key authentication, custom headers, configurable SSL verification, and response size limits.

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.

Enables LLMs to interact directly with generated REST APIs by exposing CRUD actions as MCP tools and read-only data as MCP resources.

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

An MCP server for validating JSON against schemas, checking email deliverability, verifying URLs, assessing data quality, and validating API responses using RFC-compliant checks and heuristic analysis.

Analyzes API requirements and source code, evaluates existing Postman test coverage, and generates or updates test automation with an optional draft pull request on GitHub.

Provides comprehensive development tools for Magic-API including documentation lookup, API testing, resource management, debugging with breakpoints, backup operations, and code search capabilities. Enables developers to efficiently build, test, and maintain Magic-API projects through natural language interactions.

An MCP server that crawls API documentation websites and exposes their content to AI models, enabling them to search, browse, and reference API specifications.

Enables agents to discover how a website serves its data, verify sources with evidence, export OpenAPI 3.1, and generate tested TypeScript or Python clients.

Enables users to test and interact with REST API endpoints from MCP-compatible clients, supporting multiple HTTP methods, authentication, custom headers, SSL verification settings, and configurable response-size limits.

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.

Enables users to test, debug, and interact with REST API endpoints from MCP clients such as Claude and Cline, with support for multiple HTTP methods, authentication, custom headers, SSL verification, and response-size limits.

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.

A Model Context Protocol server that fetches detailed API documentation from a local platform using a document ID. It enables language models to retrieve specific endpoint specifications to assist with tasks like code generation and API integration.

Enables testing and interacting with any REST API endpoint directly from MCP clients like Claude and Cline, supporting GET, POST, PUT, DELETE and PATCH requests with detailed response information, custom headers, and Basic, Bearer or API key authentication.

Enables users to test and interact with REST API endpoints directly from MCP clients, with support for GET, POST, PUT, DELETE, and PATCH requests, authentication, custom headers, SSL verification, and response-size limits.

Exposes Bruno API collections as Model Context Protocol (MCP) tools, allowing AI agents and MCP clients to interact with your API collections.

Transforms OpenAPI specs into an MCP server, enabling dynamic API interaction through natural language with automatic authentication and endpoint discovery.

Enables users to expose selected HTTP API endpoints as validated tools for MCP clients from a single JSON config file, with built-in timeouts, structured error messages, image responses, and disclaimers.

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

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

Enables LLMs to discover and use generated REST API services as Model Context Protocol tools and resources, supporting CRUD actions and read-only data access without custom glue code.

An MCP Server that enables interaction with Google's Public Certificate Authority API for managing publicly trusted TLS certificates via natural language.

This MCP server enables interaction with Google's Verified Access API, allowing users to verify the security posture of Chrome OS and Chrome Browser devices through natural language commands.

An MCP Server that enables interaction with the Obono RKSV API, automatically generated using AG2's MCP builder to provide a standardized way to access the functionality defined in the OpenAPI specification.

MCP server for making API calls with authentication support. Allows configuring multiple API endpoints and performing GET, POST, PUT, DELETE requests, including form data and file uploads.