localhostmcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| requestA | Sends an HTTP request to localhost at given port, with given HTTP method, request body, and headers. Parametersport : int Port to send request to (e.g. port=8000 hits http://localhost:8000). path : str Path to send request to (e.g. path=/foo/bar hits http://localhost:{port}/foo/bar). method : str, HTTP method for request (e.g. GET, POST). data : str, optional HTTP request body. Note: content type header is not set automatically, and must be set through "headers". headers : dict, optional HTTP headers (e.g. {"Content-Type": "application/json"}). Returnsint Response status code. str Response data. |
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
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming is trivially consistent.
One tool for making HTTP requests to localhost is slightly thin but appropriate for a focused utility.
Covers core HTTP request parameters (method, path, data, headers) but limited to localhost and lacks automatic content-type handling.