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

# Troubleshoot the Meow MCP server: connection and auth errors

> Fix common Meow MCP issues: tools not appearing, network egress, OAuth re-authentication, scope and permission errors, drafted transfers, and getting support.

Solutions to the most common issues connecting to and using the Meow MCP server. If you're stuck, [contact support](mailto:support@meow.com) with the request ID from the error response.

## Tools don't appear after connecting

<AccordionGroup>
  <Accordion title="Network egress is disabled" icon="globe">
    Most clients block outbound network access by default. Enable it:

    * **Claude.ai**: Settings → Capabilities, allow network egress.
    * **Claude Code**: Settings → Capabilities → **Allow network egress** → **All domains**.

    Reconnect the server after enabling egress.
  </Accordion>

  <Accordion title="The server needs authentication" icon="lock">
    If the client reports the server as unauthenticated (an HTTP 401 or 403), complete the sign-in flow. In Claude Code, run `/mcp` and follow the browser prompt. See [Authentication](/mcp/authentication).
  </Accordion>

  <Accordion title="Wrong transport or URL" icon="link">
    The Meow MCP server uses **HTTP** transport. Confirm your config uses `"type": "http"` where required and one of `https://mcp.meow.com` (OAuth) or `https://mcp.meow.com/cli` (CLI). See [Connect a client](/mcp/connect).
  </Accordion>
</AccordionGroup>

## Authentication & permission errors

<AccordionGroup>
  <Accordion title="A tool returns 'not authorized' or a permission error" icon="ban">
    The effective permission is the intersection of your role and the scopes you granted. If an action fails:

    * Check `get_session_info` to see your role and granted scopes.
    * Reconnect and grant the needed scope (for example, `meow.transfers`) in the [scope picker](/mcp/authentication#choose-what-to-share).
    * Confirm your role on the target entity actually allows the action. Granting a scope never exceeds your role.
  </Accordion>

  <Accordion title="The scope I need isn't offered at connect time" icon="eye-slash">
    The scope picker hides scopes your role can't use on any entity. If `meow.transfers`, `meow.cards`, or `meow.billing` doesn't appear, your role lacks that permission. Ask an admin to adjust it.
  </Accordion>

  <Accordion title="My assistant suddenly lost access" icon="rotate">
    The session may have been [revoked](/mcp/authentication#revoking-access) from the dashboard, or the token expired. Reconnect to start a fresh OAuth flow. Multi-factor requirements are also enforced per call.
  </Accordion>

  <Accordion title="API key on the CLI surface is rejected" icon="key">
    Confirm the key is active and carries the scopes the assistant needs. Create and scope keys from the [dashboard](https://www.meow.com/dashboard). See [API key authentication](/authentication).
  </Accordion>
</AccordionGroup>

## Payments & cards

<AccordionGroup>
  <Accordion title="My transfer didn't go through" icon="hourglass">
    That's expected. MCP transfers are drafts that sit in a pending-approval state until a human approves them on the [Meow dashboard](https://app.meow.com/signin). Check status with `get_approval`. See [Human-in-the-loop approvals](/mcp/security#human-in-the-loop-approvals).
  </Accordion>

  <Accordion title="update_card isn't available" icon="pen">
    `update_card` is exposed on the **OAuth surface** only (`mcp.meow.com`). On the CLI surface, revoke and reissue instead.
  </Accordion>
</AccordionGroup>

## Error format & getting support

MCP tool errors mirror the [REST API error format](/errors): a JSON body with `code`, `message`, and `debug_message`. Every response also carries a request ID.

When contacting [support@meow.com](mailto:support@meow.com), include:

* The request ID from the error response
* The tool name and surface (OAuth or CLI)
* What you asked the assistant to do

## Next steps

<CardGroup cols={2}>
  <Card title="Tool reference" icon="wrench" href="/mcp/tools">
    Every tool and the scope it requires.
  </Card>

  <Card title="Changelog" icon="clock-rotate-left" href="/changelog/mcp">
    New MCP capabilities over time.
  </Card>
</CardGroup>