search_ecosystems — devstack mcp MCP Tool Read-only
search_ecosystems
(search ecosystems) is one of 10 tools on the
devstack mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_ecosystems from your client
- Claude Code devstack mcp search_ecosystems run in your project directory
- Claude Desktop devstack mcp search_ecosystems ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor devstack mcp search_ecosystems ~/.cursor/mcp.json
- VS Code devstack mcp search_ecosystems .vscode/mcp.json
- Zed devstack mcp search_ecosystems ~/.config/zed/settings.json
- Windsurf devstack mcp search_ecosystems ~/.codeium/windsurf/mcp_config.json
- Cline devstack mcp search_ecosystems ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI devstack mcp search_ecosystems ~/.gemini/settings.json
- Grok devstack mcp search_ecosystems .mcp.json (in your project root)
- ChatGPT devstack mcp search_ecosystems Settings → Connectors → Advanced → Developer mode
- Claude.ai devstack mcp search_ecosystems Settings → Connectors → Add custom connector
- LangChain devstack mcp search_ecosystems pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http devstack-mcp https://devstack-mcp.vercel.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.