everyinfra_list_requests — EveryInfra MCP Tool
everyinfra_list_requests
(everyinfra list requests) is one of 12 tools on the
EveryInfra
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call everyinfra_list_requests from your client
- Claude Code EveryInfra everyinfra_list_requests run in your project directory
- Claude Desktop EveryInfra everyinfra_list_requests ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EveryInfra everyinfra_list_requests ~/.cursor/mcp.json
- VS Code EveryInfra everyinfra_list_requests .vscode/mcp.json
- Zed EveryInfra everyinfra_list_requests ~/.config/zed/settings.json
- Windsurf EveryInfra everyinfra_list_requests ~/.codeium/windsurf/mcp_config.json
- Cline EveryInfra everyinfra_list_requests ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EveryInfra everyinfra_list_requests ~/.gemini/settings.json
- Grok EveryInfra everyinfra_list_requests .mcp.json (in your project root)
- ChatGPT EveryInfra everyinfra_list_requests Settings → Connectors → Advanced → Developer mode
- Claude.ai EveryInfra everyinfra_list_requests Settings → Connectors → Add custom connector
- LangChain EveryInfra everyinfra_list_requests pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http everyinfra https://api.everyinfra.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.