> ## Documentation Index
> Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Why won't my assistant connect?

> Fix common Klipy MCP issues: OAuth sign-in failures, a connector showing old or missing tools, tools blocked by a missing scope, and checking token usage.

Most Klipy MCP problems fall into one of four buckets: sign-in, a stale tool catalog, a missing scope, or token usage. Work through the matching section below.

## 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](https://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.

<Note>
  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.
</Note>

## 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.

<Warning>
  If your connector shows tools that no longer match this reference, **remove the Klipy connector and add it again**. Re-adding forces your client to fetch the current tool catalog. This is a client-side cache, not a Klipy outage.
</Warning>

## A tool is missing from the catalog

Each tool is gated by a [scope](/docs/guides/mcp/overview#scopes). 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:

1. Remove the Klipy connector in your client.
2. Add it again to trigger a fresh OAuth consent screen.
3. Check the scope that unlocks the tool you need, then finish the flow.

For example, sending requires `messages:send`, and accepting or rejecting agent suggestions requires `agent:write`. The [tool reference](/docs/guides/mcp/tools) 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 call `get_token_usage`. It reports your subscription tier, remaining token budget, and whether token consumption is currently suspended.

<Note>
  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](/docs/guides/billing/managing-usage) for the full model.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Overview" icon="book-open" href="/docs/guides/mcp/overview">
    How the Klipy MCP server works, and the scopes you grant on connect.
  </Card>

  <Card title="Tool reference" icon="wrench" href="/docs/guides/mcp/tools">
    Every tool Claude can call, grouped by scope.
  </Card>
</CardGroup>