patterns/coordinator_election.md — Topology Index MCP Resource
patterns/coordinator_election.md
is one of 114 resources on the
Topology Index
MCP server. Connect the server and your client can attach it as context.
by client
How to attach patterns/coordinator_election.md from your client
- Claude Code Topology Index Resource/patterns/coordinator_election.md run in your project directory
- Claude Desktop Topology Index Resource/patterns/coordinator_election.md ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Topology Index Resource/patterns/coordinator_election.md ~/.cursor/mcp.json
- VS Code Topology Index Resource/patterns/coordinator_election.md .vscode/mcp.json
- Zed Topology Index Resource/patterns/coordinator_election.md ~/.config/zed/settings.json
- Windsurf Topology Index Resource/patterns/coordinator_election.md ~/.codeium/windsurf/mcp_config.json
- Cline Topology Index Resource/patterns/coordinator_election.md ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Topology Index Resource/patterns/coordinator_election.md ~/.gemini/settings.json
- Grok Topology Index Resource/patterns/coordinator_election.md .mcp.json (in your project root)
- ChatGPT Topology Index Resource/patterns/coordinator_election.md Settings → Connectors → Advanced → Developer mode
- Claude.ai Topology Index Resource/patterns/coordinator_election.md Settings → Connectors → Add custom connector
- LangChain Topology Index Resource/patterns/coordinator_election.md pip install langchain-mcp-adapters
Other resources on this server
- index
- llms.txt
- patterns/index.md
- patterns/single_agent.md
- patterns/fan_out.md
- patterns/map_reduce.md
- patterns/independent_workers.md
- patterns/lane_swarm.md
- patterns/supervisor.md
- patterns/planner_worker.md
- patterns/role_pipeline.md
- patterns/hierarchical_delegation.md
- patterns/blackboard.md
- patterns/shared_ledger.md
- patterns/mailbox_network.md
- patterns/implement_review.md
- patterns/critic_loop.md
- patterns/council.md
- patterns/debate.md
- patterns/dynamic_spawning.md
- patterns/adaptive_routing.md
- patterns/tree_search.md
- patterns/architecture_search.md
- patterns/successor_handoff.md
- patterns/signed_coordination.md
- patterns/single_agent/findings.md
- patterns/fan_out/findings.md
- patterns/map_reduce/findings.md
- patterns/independent_workers/findings.md
- patterns/lane_swarm/findings.md
- patterns/supervisor/findings.md
- patterns/planner_worker/findings.md
- patterns/role_pipeline/findings.md
- patterns/hierarchical_delegation/findings.md
- patterns/blackboard/findings.md
- patterns/shared_ledger/findings.md
- patterns/mailbox_network/findings.md
- patterns/implement_review/findings.md
- patterns/critic_loop/findings.md
- patterns/council/findings.md
Read from the server itself, by connecting to it and calling resources/list on 24 September 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.