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