RequestRepo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REQUESTREPO_HOST | No | The host address of the requestrepo server. | requestrepo.com |
| REQUESTREPO_PORT | No | The port for the requestrepo server. | 443 |
| REQUESTREPO_TOKEN | No | Optional auth token. If set, it is used. Otherwise a new session is created. | |
| REQUESTREPO_VERIFY | No | Whether to verify SSL certificates. | true |
| REQUESTREPO_PROTOCOL | No | The protocol to use (e.g., https). | https |
| REQUESTREPO_MAX_BYTES | No | Maximum bytes for binary fields. | 65536 |
| REQUESTREPO_ADMIN_TOKEN | No | Optional admin token used when creating a new session. | |
| REQUESTREPO_DEFAULT_TIMEOUT_SECONDS | No | Default timeout in seconds for operations. | 30 |
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 |
|---|---|
| session_infoB | Return session info for the active requestrepo client. |
| list_requestsC | List captured requests with optional filtering. |
| wait_for_requestC | Poll for a new request until timeout. |
| delete_requestC | Delete one request. |
| delete_all_requestsB | Delete all requests for the current session. |
| share_requestC | Create a share token for a request. |
| get_shared_requestC | Resolve a shared request token. |
| list_dnsB | List DNS records. |
| add_dnsC | Add a DNS record. |
| remove_dnsB | Remove DNS records by domain and optional type. |
| update_dnsC | Replace the full DNS records set. |
| list_filesB | List all file responses. |
| get_fileC | Get one file response. |
| set_fileD | Set one file response. |
| update_filesC | Replace all file responses. |
| pingB | Ping the underlying requestrepo websocket connection. |
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 16 tools
Most tools have distinct purposes, but some potential confusion exists between 'delete_request' and 'delete_all_requests', and 'set_file' and 'update_files' could overlap. The DNS tools (add_dns, list_dns, remove_dns, update_dns) are clearly differentiated by action, and file/request tools generally target different operations.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. Examples include 'add_dns', 'list_requests', 'update_files', and 'wait_for_request'. There are no deviations in style or convention across the set.
With 16 tools, the count is slightly high but reasonable for a server handling requests, DNS, and files. It covers multiple domains without being excessive, though it might feel heavy compared to simpler servers. The tools appear well-scoped to the server's purpose.
The tool set provides good coverage for request management (list, delete, share, wait), DNS operations (add, list, remove, update), and file handling (get, list, set, update). Minor gaps include no explicit 'get_request' tool and limited session management beyond 'session_info', but agents can work around these with existing tools.