commons_review_requests — BEACON Commons MCP Tool
commons_review_requests
(commons review requests) is one of 16 tools on the
BEACON Commons
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call commons_review_requests from your client
- Claude Code BEACON Commons commons_review_requests run in your project directory
- Claude Desktop BEACON Commons commons_review_requests ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BEACON Commons commons_review_requests ~/.cursor/mcp.json
- VS Code BEACON Commons commons_review_requests .vscode/mcp.json
- Zed BEACON Commons commons_review_requests ~/.config/zed/settings.json
- Windsurf BEACON Commons commons_review_requests ~/.codeium/windsurf/mcp_config.json
- Cline BEACON Commons commons_review_requests ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BEACON Commons commons_review_requests ~/.gemini/settings.json
- Grok BEACON Commons commons_review_requests .mcp.json (in your project root)
- ChatGPT BEACON Commons commons_review_requests Settings → Connectors → Advanced → Developer mode
- Claude.ai BEACON Commons commons_review_requests Settings → Connectors → Add custom connector
- LangChain BEACON Commons commons_review_requests pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http beacon-commons https://commons.beacon.methodfield.com/commons/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.