get_ecosystem_events — Machinepulse MCP Tool Read-only
get_ecosystem_events
(get ecosystem events) 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_ecosystem_events from your client
- Claude Code Machinepulse get_ecosystem_events run in your project directory
- Claude Desktop Machinepulse get_ecosystem_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Machinepulse get_ecosystem_events ~/.cursor/mcp.json
- VS Code Machinepulse get_ecosystem_events .vscode/mcp.json
- Zed Machinepulse get_ecosystem_events ~/.config/zed/settings.json
- Windsurf Machinepulse get_ecosystem_events ~/.codeium/windsurf/mcp_config.json
- Cline Machinepulse get_ecosystem_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Machinepulse get_ecosystem_events ~/.gemini/settings.json
- Grok Machinepulse get_ecosystem_events .mcp.json (in your project root)
- ChatGPT Machinepulse get_ecosystem_events Settings → Connectors → Advanced → Developer mode
- Claude.ai Machinepulse get_ecosystem_events Settings → Connectors → Add custom connector
- LangChain Machinepulse get_ecosystem_events 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.