This MCP server exposes a set of curl-based tools that allow a client to perform HTTP requests securely through the MCP protocol. Available tools include curl_get for HTTP GET requests, curl_post for HTTP POST requests, curl_custom for executing arbitrary curl commands with safety restrictions, and curl_download for downloading files with metadata. Each tool enforces safety checks such as allowed URL schemes, output size limits, and request timeouts to prevent abuse. You can interact with the server by invoking the corresponding tool (e.g., curl_get) via the MCP client, supplying the required parameters and optional headers, timeouts, and content types as described in the tool definitions.

Prerequisites:

• Node.js 18+ installed on your system
• curl command available in PATH
• TypeScript and a build environment if developing locally

Installation steps:

1. Create a project directory and enter it mkdir curl-mcp-server cd curl-mcp-server

2. Install dependencies npm install @modelcontextprotocol/sdk npm install -D typescript @types/node tsx

3. Create the source structure (as per the project): mkdir src

   Place your server code in src/index.ts

4. Build the project npm run build

5. Run in development or production modes depending on your setup npm run dev # development mode npm run build npm start # production run

Notes:

• Ensure the curl binary is accessible in your PATH on the host running the MCP server.
• Adjust build and start scripts as needed for your environment.

Tips and considerations:

• The server restricts dangerous curl flags and certain operations to protect the host (e.g., file uploads, --config usage, and binary data uploads are blocked).
• Timeouts are configurable per request with a maximum of 30 seconds; the default is 10 seconds for most operations.
• Output is capped at 1MB to prevent excessive memory usage; plan data handling accordingly.
• Only HTTP and HTTPS URLs are allowed; ensure URL validation is enforced in your client and server configuration.
• If you encounter issues, check that the MCP integration configuration matches your deployment path (e.g., correct index.js path in the Claude Desktop integration).
• Consider setting environment variables for API keys or tokens securely if your deployment environment supports it.