cURL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| curl_executeA | Execute an HTTP request using cURL with structured parameters. This tool provides a safe, structured way to make HTTP requests with common cURL options. It handles URL encoding, header formatting, and response processing automatically. Args:
jq_filter Syntax:
jq_filter Validation:
Returns: The HTTP response body, or JSON with metadata if include_metadata is true: { "success": boolean, "exit_code": number, "response": string, "stderr": string (if present), "saved_to_file": boolean (if response was saved), "filepath": string (path to saved file) } Examples:
Error Handling:
Temp File Lifecycle: Files saved with save_to_file or auto-save are:
|
| jq_queryA | Query an existing JSON file with a jq-like filter expression. This tool allows you to extract data from saved JSON files without making new HTTP requests. Useful for:
Args:
Filter Syntax:
Security:
Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| api-test | Test an API endpoint and analyze the response |
| api-discovery | Explore a REST API to discover available endpoints |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| documentation | API documentation and usage examples for the cURL MCP server |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: curl_execute handles HTTP requests, while jq_query queries saved JSON files. There is no functional overlap, making selection unambiguous.
Both tools follow a consistent verb_noun pattern in snake_case (curl_execute, jq_query). The style is uniform, promoting predictability.
With only two tools, the server feels minimal for its intended scope. While it covers core HTTP request and JSON querying functionality, additional tools (e.g., manage saved files, list responses) could enhance the surface without overloading it.
The curl_execute tool is comprehensive for HTTP requests, but the server lacks auxiliary tools such as file management (list, delete saved files) or a way to retrieve response metadata separately. This leaves minor but notable gaps for certain workflows.