"Understanding How to Use a Browser" matching MCP servers:

A zero-dependency Node.js playground for debugging how MCP clients authenticate to an MCP server over HTTP.

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 REST API code (like NestJS controllers or FastAPI endpoints) to Postman collections and environments, helping developers automatically sync their API endpoints with Postman.

A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.

Enables browser automation and API testing for AI agents using Playwright and Chrome DevTools Protocol, with numbered element references, Set-of-Mark screenshots, flow recording/replay, element memory, captcha handoff, and HTTP API test suites.

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.

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

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.

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

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

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

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

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.

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.

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

Converts natural language queries into valid GraphQL queries and executes them against GraphQL APIs. Includes schema introspection, query validation, execution with authentication, and query history tracking.

Provides a testable gateway path for running a local MCP-style server in hosted-like conditions, with tenant-isolated reads, approval-denied writes, deterministic failures, and smoke-test verification.

Enables AI assistants to search, analyze, and debug application API traffic captured by Tusk Drift, including HTTP requests, database queries, distributed traces, latency metrics, and error rates.

Free JSON Schema validation, JSON to TypeScript, CSV to JSON, JSON repair and JSON to CSV for AI agents. Hosted MCP plus local STDIO. Connect once with a scoped key; enforce tool allowlists and quotas, inspect request IDs. Runnable repair → validate → CSV workflow. Bounded OpenAPI and webhook checks. No LLM calls or payments. Setup: invokeport.com/agents.

Converts OpenAPI specifications into MCP services with HTTP header passthrough support. Enables interaction with any OpenAPI-compliant service through natural language by dynamically transforming API documentation into MCP tools.

Turn any GraphQL API into MCP tools. Zero config, zero code. Auto-introspection, flat InputObject schemas for better LLM accuracy, smart truncation, retry logic with exponential backoff.

Automatically converts any OpenAPI specification or Postman Collection into an MCP server, enabling AI assistants like Claude to directly interact with REST APIs without writing any code.

A service that converts OpenAPI specifications into MCP tools, enabling AI assistants to interact with your API endpoints through natural language.

Automatically converts any OpenAPI specification into an MCP server, exposing all HTTP endpoints as callable tools with support for various authentication methods and request types.

An MCP server that automates importing products from AliExpress, Alibaba, and Accio into DSers and pushing them to Shopify or Wix stores, with features like bulk import, pricing rules, and title cleanup.

Converts any OpenAPI/REST API into MCP tools with dynamic server switching, variable substitution, and runtime configuration. Enables seamless interaction with multiple API environments through natural language without pre-configuration.

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.

A proxy server that bridges AI agents and external APIs by dynamically translating OpenAPI specifications into standardized MCP tools, enabling seamless interaction without custom integration code.

Enables agents to navigate REST APIs through declarative maps using five verbs—ls, describe, run, find, and read—with typed operations, stored response handles, and token-efficient discovery. It can also import OpenAPI specs or learn API shapes from live calls to produce navigable maps.

A stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.

Enables testing how different MCP clients handle tool results containing both content and structuredContent, including outputSchema enforcement and mismatch scenarios.

Enables discovery, live probing, ranking, and recommendation across OpenAI-compatible gateways, measuring real latency, success, streaming, and tool-calling behavior so you can see which models actually work right now. Keeps per-model probe history to answer "which model should I use?" through tools like list_models, probe, ranking, recommend, and report.

HAL (HTTP API Layer) is a Model Context Protocol (MCP) server that provides HTTP API capabilities to Large Language Models.

A Model Context Protocol server that provides Claude Code with seamless access to Binance exchange API functionality for market data retrieval, account management, and trading operations.

An MCP server that connects to a Swagger specification and helps an AI to build all the required models to generate a MCP server for that service.

A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.

A service that dynamically generates MCP tools from Swagger/OpenAPI documentation, allowing Claude Desktop to directly invoke REST APIs through natural language.

A Model Context Protocol server that interfaces with Alpaca trading API, allowing users to manage portfolios, place trades, and access market data through natural language interactions.

Provides tools to communicate with a service dependency API, enabling users to query and interact with service relationship data and dependency mappings.