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 (onboarding only). 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.
The https://mcp.meow.com/cli surface serves signup and onboarding tools only. API keys and email codes don’t unlock account tools. Connect your client to https://mcp.meow.com and sign in with OAuth. In the Meow CLI, run meow login. See Authentication.
An onboarding key works only while the business is onboarding or under review. After the business is approved and has an active account, use OAuth or meow login instead. Requesting another email code doesn’t change this. The server also rejects the key once your membership in the business ends.
The Meow CLI now signs in through your browser. Run meow login once. If logout fails because the saved credentials are damaged, revoke Meow CLI in Developers > MCP Sessions, then run meow logout --local. See Meow CLI.

​
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.
Card tools, including update_card, are on the OAuth surface only (mcp.meow.com). Connect there, or run meow login in the Meow CLI.

​
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 onboarding)
  • What you asked the assistant to do

​
Next steps

Tool reference

Every tool and the scope it requires.

Changelog

New MCP capabilities over time.