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