Skip to main content
This page lists every tool the Meow MCP server exposes. Tools are grouped by resource. For each tool you’ll see the scope it requires and whether it is read (returns data, no side effects) or an action (changes state).
Every tool is annotated for MCP clients with a readOnlyHint or destructiveHint, so clients can show a confirmation prompt before any action runs. Read tools are marked read-only and idempotent; action tools are marked destructive. See Security & trust.
Most tools are available on both the OAuth and CLI surfaces. The few exceptions are noted in the Surface column.

​
Reading the tables

​
Entities & session

Start here. List your entities, then pass the returned entity_id to other tools. get_session_info returns your current role, entity, and granted scopes. An assistant can call it to check what it’s allowed to do before it attempts an action.

​
Accounts & balances

​
Transactions

​
Contacts

​
Cards

Read tools require meow.read; card actions require meow.cards. Cards issued through MCP are virtual cards scoped to a single merchant and spend limit. See Issuing cards below.

​
Issuing cards

create_card issues a virtual card scoped to a single merchant and spend limit. By default the card is single-use and auto-cancels after the first authorization; set single_use: false for a multi-use card that stays active until expiry or explicit revoke.
update_card is available on the OAuth surface only. On the CLI surface, revoke the card and issue a new one instead.

​
Transfers (draft only)

These tools never move money. Each one creates a payment as a draft in a pending-approval state. A human must approve it on the Meow dashboard before any funds move. The tool returns an approval reference you can check with get_approval. See Human-in-the-loop approvals.
All transfer tools require the meow.transfers scope and are available on both surfaces.

​
Bills

​
Invoices & billing

Read tools require meow.read; create tools require meow.billing.
Creating an invoice is a request for payment, not money movement. It doesn’t move funds and doesn’t need dashboard approval.

​
Tax forms, security policies & utilities

​
Account signup (CLI surface)

On the CLI surface, an assistant can open a new Meow account end-to-end. The flow is guided: call start first, then follow the step_instructions.directive returned by each response. See Agent-led signup.

​
Example prompts

Once connected, try asking your assistant:
  • “What entities do I have access to?”
  • “What are my account balances?”
  • “Show me my recent transactions for the operating account.”
  • “List my contacts.”
  • “Show me all pending bills.”
  • “Issue a single-use virtual card for $200 at AWS.”
  • “Draft an ACH transfer of $1,500 to Acme Corp.” (creates a draft you approve on the dashboard)
  • “What’s the approval status of that transfer?”

​
Next steps

Security & trust

How approvals, scopes, and auditing protect your account.

Troubleshooting

Fixes for connection, auth, and tool errors.