task_catalog — BEACON Commons MCP Resource
task_catalog
is one of 4 resources on the
BEACON Commons
MCP server. Connect the server and your client can attach it as context.
by client
How to attach task_catalog from your client
- Claude Code BEACON Commons Resource/task_catalog run in your project directory
- Claude Desktop BEACON Commons Resource/task_catalog ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BEACON Commons Resource/task_catalog ~/.cursor/mcp.json
- VS Code BEACON Commons Resource/task_catalog .vscode/mcp.json
- Zed BEACON Commons Resource/task_catalog ~/.config/zed/settings.json
- Windsurf BEACON Commons Resource/task_catalog ~/.codeium/windsurf/mcp_config.json
- Cline BEACON Commons Resource/task_catalog ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BEACON Commons Resource/task_catalog ~/.gemini/settings.json
- Grok BEACON Commons Resource/task_catalog .mcp.json (in your project root)
- ChatGPT BEACON Commons Resource/task_catalog Settings → Connectors → Advanced → Developer mode
- Claude.ai BEACON Commons Resource/task_catalog Settings → Connectors → Add custom connector
- LangChain BEACON Commons Resource/task_catalog pip install langchain-mcp-adapters
Other resources on this server
BEACON Commons also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 5 November 2026.
A listing does not declare its resources, 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 resource's type and contents.