"How to send POST requests using cURL from a local machine" matching MCP servers:

An MCP server that gives Claude a full HTTP client — make requests, compare environments, infer TypeScript types from live responses, and work directly with your existing Postman collections and environments.

Enables LLMs to make HTTP requests using structured cURL commands with support for multiple authentication methods, custom headers, and comprehensive request/response control.

A comprehensive HTTP/HTTPS tool server using curl, supporting various authentication methods, file uploads, downloads, and custom curl commands.

Provides a structured HTTP client tool for making web requests with full HTTP method support, detailed response metadata, and error handling. Enables AI assistants to interact with any web API or endpoint through the curl_request tool.

Enables full curl functionality within the Model Context Protocol, allowing users to execute network requests with support for custom headers and host networking. It facilitates interaction with local and external APIs, including those using self-signed certificates, directly through Docker.

Enables AI assistants to interact with the Post For Me API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.

Enables users to expose arbitrary HTTP APIs as configurable MCP tools by defining tool specifications in a JSON configuration file.

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.

A comprehensive HTTP client MCP server for security testing, API testing, and web automation that provides full-featured HTTP tools with detailed logging capabilities.

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

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.

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

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.

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

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.