For agents / Connection

MCP setup

Connect your AI client to your ledger. It can read entries, propose expenses or income, and directly add complete structured data. Proposals stay pending unless explicitly confirmed.

One server URL

https://staging.glidzr.com/api/mcp

Use an MCP client that supports Streamable HTTP and OAuth. Sign in to your Proof Entry account and approve the connection when prompted. The client discovers the authorization server and obtains its own token.

If Google sign-in recovers an unverified account, its previous agent connections are revoked. Connect again to authorize a new token.

Terminal

claude mcp add --transport http proofentry https://staging.glidzr.com/api/mcp

1Run it once. Add --scope user to have it in every project.
2Then /mcp inside Claude Code to sign in. A browser tab opens, you approve, and the client holds the token from then on.

For a CLI without a browser callback, use device-code authorization.

Authentication and discovery

Proof Entry uses OAuth 2.1 with PKCE and dynamic client registration. An unauthenticated MCP POST returns 401 with a WWW-Authenticate header pointing to protected resource metadata. Opening the transport URL with a browser GET returns 405; use this page for setup.

Requests are rate limited, including before authentication. A 429 may precede the OAuth challenge; wait for Retry-After when provided. JSON bodies are limited to 64 KiB and batches to 20 calls. Authenticated calls share an allowance of 120 per user per minute and 600 per IP per minute.

Your review stays in the loop

Use add_income or add_expense to record complete structured data, or pass confirm: true to log_income or log_expense. Both tool pairs accept true or false: add tools default to true, and log tools default to false. Pass confirm: false to a direct-add tool to create a pending proposal. No tool assigns a project or creates a recurring instruction. All ledger access is scoped to the account that authorized the connection.

Browse the tool catalog and input schemas, or use the same token with the HTTP API.