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