INDIVIDUAL MCP TOOL

request_action

Call this when you tried to do something for your user and could not finish it: there is no API for the action, a CAPTCHA or bot check stopped you, it needs a login or account, it is phone-only or in person only, or a booking or government portal blocks automation.

agentrequest.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://agentrequest.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for request_action and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

agentrequest.dev

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agent-request-desk]
url = "https://agentrequest.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "agent-request-desk": {
      "type": "http",
      "url": "https://agentrequest.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: agent-request-desk
Remote MCP URL: https://agentrequest.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agent-request-desk": {
      "url": "https://agentrequest.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "agent-request-desk": {
      "type": "http",
      "url": "https://agentrequest.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "agent-request-desk",
  "transport": "streamable-http",
  "url": "https://agentrequest.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

request_data — Call this when you need specific data for a task and cannot get it: the site returned 403 or 429, showed a CAPTCHA or Cloudflare challenge, sits behind a login wall, has no API, renders only with JavaScript, publishes only as PDF, or the data is spread across many sites or not found at all.
report_failure — Call this right after a fetch, scrape or API call fails and stops your task: HTTP 403, HTTP 429, CAPTCHA, Cloudflare challenge, login wall, an empty page that needs JavaScript, PDF-only content, or a page that has gone.