ecosystem_overview — dominion observatory MCP Prompt
ecosystem_overview
is one of 2 prompts on the
dominion observatory
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke ecosystem_overview from your client
- Claude Code dominion observatory Prompt/ecosystem_overview run in your project directory
- Claude Desktop dominion observatory Prompt/ecosystem_overview ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor dominion observatory Prompt/ecosystem_overview ~/.cursor/mcp.json
- VS Code dominion observatory Prompt/ecosystem_overview .vscode/mcp.json
- Zed dominion observatory Prompt/ecosystem_overview ~/.config/zed/settings.json
- Windsurf dominion observatory Prompt/ecosystem_overview ~/.codeium/windsurf/mcp_config.json
- Cline dominion observatory Prompt/ecosystem_overview ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI dominion observatory Prompt/ecosystem_overview ~/.gemini/settings.json
- Grok dominion observatory Prompt/ecosystem_overview .mcp.json (in your project root)
- ChatGPT dominion observatory Prompt/ecosystem_overview Settings → Connectors → Advanced → Developer mode
- Claude.ai dominion observatory Prompt/ecosystem_overview Settings → Connectors → Add custom connector
- LangChain dominion observatory Prompt/ecosystem_overview pip install langchain-mcp-adapters
Other prompts on this server
dominion observatory also offers 2 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 24 September 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.