Skip to main content
Glama
RequestRepo MCP
by hofill

RequestRepo MCP

MCP server for requestrepo by adragos.

Scope

  • Full requestrepo tool surface (requests, sharing, DNS, files, ping)

  • Default stdio transport, optional streamable-http

  • Confirm-gated mutations (confirm=true)

  • JSON-safe bytes envelope for binary fields

Full parameter docs are in TOOLS.md.

Related MCP server: MCP HTTP Client Server

Install

python -m pip install -e .

For local development:

python -m pip install -e ".[dev]"

Configuration

  • REQUESTREPO_TOKEN (optional)

  • REQUESTREPO_ADMIN_TOKEN (optional)

  • REQUESTREPO_HOST (default requestrepo.com)

  • REQUESTREPO_PORT (default 443)

  • REQUESTREPO_PROTOCOL (default https)

  • REQUESTREPO_VERIFY (default true)

  • REQUESTREPO_DEFAULT_TIMEOUT_SECONDS (default 30)

  • REQUESTREPO_MAX_BYTES (default 65536)

Auth behavior:

  • If REQUESTREPO_TOKEN is set, it is used.

  • Otherwise a new session is created, optionally with REQUESTREPO_ADMIN_TOKEN.

Run

requestrepo-mcp --transport stdio
requestrepo-mcp --transport streamable-http --host 127.0.0.1 --port 8000 --streamable-http-path /mcp

Install In AI Clients

Codex

With token (optional, recommended if you already have one):

codex mcp add requestrepo --env REQUESTREPO_TOKEN=your-token -- requestrepo-mcp --transport stdio

Without token (creates a new session automatically):

codex mcp add requestrepo -- requestrepo-mcp --transport stdio

Check config:

codex mcp get requestrepo

Autostart note:

  • Codex starts stdio servers automatically.

  • If startup fails, register with an absolute executable path:

codex mcp add requestrepo --env REQUESTREPO_TOKEN=your-token -- /absolute/path/to/requestrepo-mcp --transport stdio

Claude Code / Claude Desktop

{
  "mcpServers": {
    "requestrepo": {
      "command": "requestrepo-mcp",
      "args": ["--transport", "stdio"],
      "env": {
        "REQUESTREPO_TOKEN": "your-token"
      }
    }
  }
}

Cursor

{
  "mcpServers": {
    "requestrepo": {
      "command": "requestrepo-mcp",
      "args": ["--transport", "stdio"],
      "env": {
        "REQUESTREPO_TOKEN": "your-token"
      }
    }
  }
}

VS Code (Copilot Agent)

.vscode/mcp.json:

{
  "servers": {
    "requestrepo": {
      "type": "stdio",
      "command": "requestrepo-mcp",
      "args": ["--transport", "stdio"],
      "env": {
        "REQUESTREPO_TOKEN": "your-token"
      }
    }
  }
}

Tool Summary

  • session_info

  • list_requests

  • wait_for_request

  • delete_request

  • delete_all_requests

  • share_request

  • get_shared_request

  • list_dns

  • add_dns

  • remove_dns

  • update_dns

  • list_files

  • get_file

  • set_file

  • update_files

  • ping

Mutation tools require confirm=true.

Testing

pytest -q

CI runs tests on push and pull requests (see .github/workflows/ci.yml).

Available Tools

16 tools
add_dnsC

Add a DNS record.

Inputs: domain (required), record_type (required), value (required), confirm (required). Returns: object

delete_all_requestsB

Delete all requests for the current session.

Inputs: confirm (required). Returns: object

delete_requestC

Delete one request.

Inputs: request_id (required), confirm (required). Returns: object

get_fileC

Get one file response.

Inputs: path (required), decode_base64, max_bytes. Returns: object

get_shared_requestC

Resolve a shared request token.

Inputs: share_token (required), include_raw, include_body, max_bytes. Returns: object

list_dnsB

List DNS records.

Inputs: no named parameters. Returns: object

list_filesB

List all file responses.

Inputs: no named parameters. Returns: object

list_requestsC

List captured requests with optional filtering.

Inputs: limit, offset, request_type, include_raw, +2 more. Returns: object

pingB

Ping the underlying requestrepo websocket connection.

Inputs: no named parameters. Returns: object

remove_dnsB

Remove DNS records by domain and optional type.

Inputs: domain (required), record_type, confirm. Returns: object

session_infoB

Return session info for the active requestrepo client.

Inputs: include_token. Returns: object

set_fileD

Set one file response.

Inputs: path (required), confirm (required), body_text, body_base64, +2 more. Returns: object

share_requestC

Create a share token for a request.

Inputs: request_id (required). Returns: object

update_dnsC

Replace the full DNS records set.

Inputs: records (required), confirm (required). Returns: object

update_filesC

Replace all file responses.

Inputs: files (required), confirm (required). Returns: object

wait_for_requestC

Poll for a new request until timeout.

Inputs: request_type, timeout_seconds, poll_interval_seconds, include_raw, +2 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    TDQS

    C2.8/5.0

    Scored across 16 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables AI assistants to control HTTP Toolkit for intercepting, inspecting, and debugging HTTP(S) traffic from browsers, mobile devices, and Docker containers. It provides tools for server management, interceptor activation, and sending HTTP requests through natural language commands.
      23
      18 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP tool server that gives any AI agent the ability to search, scrape, and analyze content across the internet.
      42
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI agents to intercept, inspect, and modify HTTP traffic, with tools for searching, filtering, and managing captured requests and interceptors.
      11 npm
      8
      MIT