mcp-http
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_MAX_BODY | No | Maximum response body bytes returned to the agent | 1000000 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| http_requestA | Send an arbitrary HTTP request and return the response. Single generic HTTP client tool: the agent picks the method, URL, headers, query parameters and body. Returns status, headers, content-type and body. Supported methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlapping purposes. The http_request tool has a clear, distinct role as a generic HTTP client.
The tool name 'http_request' is a clear verb_noun pattern. Since there is only one tool, consistency is trivially maintained, and the name accurately reflects its function.
While a single tool feels thin, it is justified for a focused HTTP client server. The tool is comprehensive and not trivial, but the server offers no additional utilities or convenience wrappers.
The http_request tool supports all common HTTP methods, headers, query parameters, and body payloads, and returns status, headers, and body content. This fully covers the expected domain of an HTTP client with no obvious gaps.