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