"Adding a remote MCP server to Claude Desktop using HTTP+SSE" matching MCP servers:

Provides a generic HTTP client tool allowing AI agents to make arbitrary HTTP requests from their environment, with support for environment-variable placeholders for secrets.

Enables LLMs to make HTTP requests with OAuth2, session cookies, retry logic, and cURL command generation, while providing security features like SSRF protection and TLS enforcement.

Implements a Model Context Protocol server using Server-Sent Events for real-time communication with OAuth 2.1 integration via Ory Network, enabling secure AI model communication with authentication and client management.

Enables MCP clients to connect over HTTP/SSE, call simple echo, arithmetic, uppercasing, and time tools, and run asynchronous tasks with approval elicitations via the Tasks extension.

An MCP server that provides HTTP client capabilities with support for full HTTP methods, custom headers, query parameters, request bodies, and configurable timeouts.

Mock HTTP server implementing MCP (Model Context Protocol) with streamable HTTP transport, health endpoint, and example tools like echo and time.

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.

HTTP Inspector MCP Server enables sending arbitrary HTTP requests, viewing history via a web panel, and taking screenshots of the panel for AI penetration testing workflows.

Enables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.

Enables agents to submit request/response header literals over stdio and receive deterministic, specification-derived verdicts on CORS, RFC 9111 cache freshness, RFC 9110 conditional requests, and Vary matching, complete with rule IDs and clause references. Runs entirely offline with no third-party runtime dependencies, returning byte-identical output for identical input.

Stateful interactive HTTP REPL and Agentic MCP engine for API navigation and testing.

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.

A bridge server that converts stdio protocol to streamable-http protocol, allowing clients to interact with MCP services over HTTP.

A powerful MCP server for making HTTP requests, GraphQL queries, and TCP/Telnet connections from AI assistants.

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.

Provides a standardized MCP interface for interacting with HTTP tools and services, enabling unified API access and management.

Enables MCP clients to verify publisher acceptance fixtures over Streamable HTTP by exposing an identify tool that returns the fixture name, version, transport, and supplied message.

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

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.