OAuth sign-in fails
If the consent screen never appears, closes without connecting, or your client reports an authentication error:- Confirm the endpoint is exactly
https://api.klipy.ai/mcp. A trailing path or a typo sends the client to the wrong place. - Make sure you are signed in to Klipy at app.klipy.ai in the same browser your client opens for OAuth. The consent screen authorizes the account you are logged into.
- Complete the consent screen fully. Check at least the scopes your workflow needs and finish the flow — closing the tab early leaves the connection unauthorized.
- If a previous attempt left a broken connection, remove the Klipy connector in your client and add it again from a clean state.
Klipy MCP is generally available to any Klipy account, so there is no plan or beta gate to clear. If sign-in still fails after the steps above, the issue is with the connection or the client, not your account tier.
Connector shows old or missing tools
Klipy updates its tool catalog over time. Many MCP clients cache the catalog they fetched when you first connected, so after a Klipy update your connector can keep showing an outdated set of tools — or miss newly added ones.A tool is missing from the catalog
Each tool is gated by a scope. Your connection can only see and call the tools whose scopes you approved on the consent screen. If an expected tool never appears — for example,send_message_draft is absent even though drafting tools are present — the grant behind that connection is missing the tool’s scope.
To fix it, re-consent with the required scope checked:
- Remove the Klipy connector in your client.
- Add it again to trigger a fresh OAuth consent screen.
- Check the scope that unlocks the tool you need, then finish the flow.
messages:send, and accepting or rejecting agent suggestions requires agent:write. The tool reference lists the gating scope for every tool.
Check your token usage
Reading data and preparing drafts do not consume tokens — tokens are spent only when a user accepts an action, such as sending a draft. If actions start failing for a budget reason, ask your agent to callget_token_usage. It reports your subscription tier, remaining token budget, and whether token consumption is currently suspended.
If
get_token_usage reports is_unlimited: true, your account has no token cap — ignore the remaining-token value rather than reading a low number as a limit. See Managing your usage for the full model.Next steps
Overview
How the Klipy MCP server works, and the scopes you grant on connect.
Tool reference
Every tool Claude can call, grouped by scope.