Skip to main content
Solutions to the most common issues connecting to and using the Meow MCP server. If you’re stuck, contact support with the request ID from the error response.

​
Tools don’t appear after connecting

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

​
Authentication & permission errors

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.
  • Confirm your role on the target entity actually allows the action. Granting a scope never exceeds your role.
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.
The session may have been revoked from the dashboard, or the token expired. Reconnect to start a fresh OAuth flow. Multi-factor requirements are also enforced per call.
Confirm the key is active and carries the scopes the assistant needs. Create and scope keys from the dashboard. See API key authentication.

​
Payments & cards

That’s expected. MCP transfers are drafts that sit in a pending-approval state until a human approves them on the Meow dashboard. Check status with get_approval. See Human-in-the-loop approvals.
update_card is exposed on the OAuth surface only (mcp.meow.com). On the CLI surface, revoke and reissue instead.

​
Error format & getting support

MCP tool errors mirror the REST API error format: a JSON body with code, message, and debug_message. Every response also carries a request ID. When contacting 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

Tool reference

Every tool and the scope it requires.

Changelog

New MCP capabilities over time.