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