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

# Meow MCP tool reference: accounts, cards, transfers, billing

> Every tool the Meow MCP server exposes, grouped by resource: accounts, balances, transactions, contacts, cards, transfers, billing, with required scopes.

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

<Note>
  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](/mcp/security).
</Note>

Most tools are available on **both** the OAuth and CLI surfaces. The few exceptions are noted in the Surface column.

## Reading the tables

| Column      | Meaning                                                                                                          |
| ----------- | ---------------------------------------------------------------------------------------------------------------- |
| **Tool**    | The tool name (operation ID) the assistant calls                                                                 |
| **Scope**   | The [scope](/mcp/authentication#scopes) required: `meow.read`, `meow.transfers`, `meow.cards`, or `meow.billing` |
| **Type**    | **Read** or **Action**                                                                                           |
| **Surface** | Both, OAuth only, or CLI only                                                                                    |

## Entities & session

Start here. List your entities, then pass the returned `entity_id` to other tools.

| Tool               | Scope       | Type | Surface |
| ------------------ | ----------- | ---- | ------- |
| `list_my_entities` | `meow.read` | Read | OAuth   |
| `get_my_entity`    | `meow.read` | Read | CLI     |
| `get_session_info` | `meow.read` | Read | Both    |

`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

| Tool                            | Scope       | Type | Surface |
| ------------------------------- | ----------- | ---- | ------- |
| `list_bank_accounts`            | `meow.read` | Read | Both    |
| `get_bank_account`              | `meow.read` | Read | Both    |
| `get_account_balances`          | `meow.read` | Read | Both    |
| `list_account_payment_networks` | `meow.read` | Read | Both    |

## Transactions

| Tool                           | Scope       | Type | Surface |
| ------------------------------ | ----------- | ---- | ------- |
| `list_account_transactions`    | `meow.read` | Read | Both    |
| `get_usdc_transaction`         | `meow.read` | Read | Both    |
| `get_ach_transfer`             | `meow.read` | Read | Both    |
| `get_wire_transfer`            | `meow.read` | Read | Both    |
| `list_scheduled_ach_transfers` | `meow.read` | Read | Both    |

## Contacts

| Tool            | Scope       | Type | Surface |
| --------------- | ----------- | ---- | ------- |
| `list_contacts` | `meow.read` | Read | Both    |
| `get_contact`   | `meow.read` | Read | Both    |

## 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](#issuing-cards) below.

| Tool                     | Scope        | Type   | Surface |
| ------------------------ | ------------ | ------ | ------- |
| `list_cards`             | `meow.read`  | Read   | Both    |
| `list_card_transactions` | `meow.read`  | Read   | Both    |
| `get_card_insights`      | `meow.read`  | Read   | Both    |
| `get_card`               | `meow.read`  | Read   | Both    |
| `get_card_details`       | `meow.read`  | Read   | Both    |
| `create_card`            | `meow.cards` | Action | Both    |
| `update_card`            | `meow.cards` | Action | OAuth   |
| `revoke_card`            | `meow.cards` | Action | Both    |

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

<Note>
  `update_card` is available on the OAuth surface only. On the CLI surface, revoke the card and issue a new one instead.
</Note>

## Transfers (draft only)

<Note>
  **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](https://app.meow.com/signin) before any funds move. The tool returns an approval reference you can check with `get_approval`. See [Human-in-the-loop approvals](/mcp/security#human-in-the-loop-approvals).
</Note>

All transfer tools require the `meow.transfers` scope and are available on both surfaces.

| Tool                            | Scope            | Type           | Drafts                                       |
| ------------------------------- | ---------------- | -------------- | -------------------------------------------- |
| `create_ach_transfer`           | `meow.transfers` | Action (draft) | ACH transfer to a counterparty               |
| `create_scheduled_ach_transfer` | `meow.transfers` | Action (draft) | Scheduled ACH transfer                       |
| `create_wire_transfer`          | `meow.transfers` | Action (draft) | Wire transfer                                |
| `create_book_transfer`          | `meow.transfers` | Action (draft) | Internal book transfer between your accounts |
| `create_crypto_transaction`     | `meow.transfers` | Action (draft) | USDC transfer to a contact                   |
| `get_approval`                  | `meow.read`      | Read           | Checks a draft's approval status             |

## Bills

| Tool         | Scope       | Type | Surface |
| ------------ | ----------- | ---- | ------- |
| `list_bills` | `meow.read` | Read | Both    |
| `get_bill`   | `meow.read` | Read | Both    |

## Invoices & billing

Read tools require `meow.read`; create tools require `meow.billing`.

| Tool                        | Scope          | Type   | Surface |
| --------------------------- | -------------- | ------ | ------- |
| `list_products`             | `meow.read`    | Read   | Both    |
| `get_product`               | `meow.read`    | Read   | Both    |
| `create_product`            | `meow.billing` | Action | OAuth   |
| `list_invoicing_customers`  | `meow.read`    | Read   | Both    |
| `get_invoicing_customer`    | `meow.read`    | Read   | Both    |
| `create_invoicing_customer` | `meow.billing` | Action | OAuth   |
| `list_payment_method_types` | `meow.read`    | Read   | Both    |
| `list_invoices`             | `meow.read`    | Read   | Both    |
| `get_invoice`               | `meow.read`    | Read   | Both    |
| `list_invoice_line_items`   | `meow.read`    | Read   | Both    |
| `get_invoice_line_item`     | `meow.read`    | Read   | Both    |
| `create_invoice`            | `meow.billing` | Action | OAuth   |
| `list_collection_accounts`  | `meow.read`    | Read   | Both    |

<Note>
  Creating an invoice is a request for payment, not money movement. It doesn't move funds and doesn't need dashboard approval.
</Note>

## Tax forms, security policies & utilities

| Tool                      | Scope       | Type | Surface |
| ------------------------- | ----------- | ---- | ------- |
| `search_tax_forms`        | `meow.read` | Read | Both    |
| `get_tax_form`            | `meow.read` | Read | Both    |
| `list_security_policies`  | `meow.read` | Read | Both    |
| `validate_routing_number` | `meow.read` | Read | Both    |

## 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](/mcp/connect#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

<CardGroup cols={2}>
  <Card title="Security & trust" icon="shield-check" href="/mcp/security">
    How approvals, scopes, and auditing protect your account.
  </Card>

  <Card title="Troubleshooting" icon="bug" href="/mcp/troubleshooting">
    Fixes for connection, auth, and tool errors.
  </Card>
</CardGroup>