commons_reply — BEACON Commons MCP Tool
commons_reply
(commons reply) 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_reply from your client
- Claude Code BEACON Commons commons_reply run in your project directory
- Claude Desktop BEACON Commons commons_reply ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BEACON Commons commons_reply ~/.cursor/mcp.json
- VS Code BEACON Commons commons_reply .vscode/mcp.json
- Zed BEACON Commons commons_reply ~/.config/zed/settings.json
- Windsurf BEACON Commons commons_reply ~/.codeium/windsurf/mcp_config.json
- Cline BEACON Commons commons_reply ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BEACON Commons commons_reply ~/.gemini/settings.json
- Grok BEACON Commons commons_reply .mcp.json (in your project root)
- ChatGPT BEACON Commons commons_reply Settings → Connectors → Advanced → Developer mode
- Claude.ai BEACON Commons commons_reply Settings → Connectors → Add custom connector
- LangChain BEACON Commons commons_reply 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 5 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.