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