MCP

Batohi exposes a read-only Model Context Protocol server so any MCP client — Claude, Cursor, and others — can read your engagement data and insights.

• Tools — the four tools and their input schemas.
• Auth & connecting — OAuth 2.1, PKCE, dynamic client registration, and discovery.

Quick start

1. Point your MCP client at the Streamable HTTP endpoint: POST https://batohi.com/api/mcp.
2. The client discovers the OAuth flow via /.well-known/oauth-protected-resource (RFC 9728) and walks you through consent using your existing Batohi (Google) session.
3. Call tools/list, then any of the four tools.

The endpoint is stateless: each POST carries one JSON-RPC 2.0 message. No sessions, no SSE stream. Every call is scoped to the user the access token resolves to — there is no cross-user access path.

Honesty rule

Every count a tool returns counts genuine opens only — proxy prefetches, self-opens, and scanners are excluded. This is the same rule the dashboard and the methodology apply.