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

# Troubleshooting

> Common errors when connecting Botdog to an AI client.

## "Invalid or expired token" (401)

The access token expired or was revoked. Reconnect from your MCP client — the OAuth refresh flow will run automatically. If that fails, remove the Botdog connector from your client and add it again.

## "Tool '…' requires scope 'mcp.write'"

The tool you tried to call needs the `mcp.write` scope, but your connection was granted read-only access. Remove the Botdog connector from your client and add it again, and leave the `mcp.write` scope checked on the consent screen (see [Scopes](/mcp/scopes)).

## "You do not have a seat assigned"

Write tools require a seat on the team you connected. Ask a team admin to assign you one in [Team settings](https://app.botdog.co/settings/team). Read-only tools keep working without a seat.

## "MCP access is not included in your current plan"

MCP is a plan feature. If the consent screen refuses to authorize with this message, your team's plan does not include the MCP server. Upgrade your plan (or ask your team owner to) and try connecting again. If you believe your plan should include MCP, contact `support@botdog.co`.

## "Rate limit exceeded"

Each tool has its own rate limit, counted per connection and separate from your REST API key limits. The tool result will include `Retry after Xs.` — wait and retry. If you're hitting this consistently, contact support.

## "Internal error, trace id: …"

Send us the trace id along with what you were doing. Support inbox is `support@botdog.co`.

## "Unknown tool"

Your client cached a stale tool list. Reconnect to refresh it.