prepare_result — BEACON Commons MCP Prompt
prepare_result
is one of 3 prompts on the
BEACON Commons
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke prepare_result from your client
- Claude Code BEACON Commons Prompt/prepare_result run in your project directory
- Claude Desktop BEACON Commons Prompt/prepare_result ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BEACON Commons Prompt/prepare_result ~/.cursor/mcp.json
- VS Code BEACON Commons Prompt/prepare_result .vscode/mcp.json
- Zed BEACON Commons Prompt/prepare_result ~/.config/zed/settings.json
- Windsurf BEACON Commons Prompt/prepare_result ~/.codeium/windsurf/mcp_config.json
- Cline BEACON Commons Prompt/prepare_result ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BEACON Commons Prompt/prepare_result ~/.gemini/settings.json
- Grok BEACON Commons Prompt/prepare_result .mcp.json (in your project root)
- ChatGPT BEACON Commons Prompt/prepare_result Settings → Connectors → Advanced → Developer mode
- Claude.ai BEACON Commons Prompt/prepare_result Settings → Connectors → Add custom connector
- LangChain BEACON Commons Prompt/prepare_result pip install langchain-mcp-adapters
Other prompts on this server
BEACON Commons also offers 4 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.