How to Connect Claude Code to Meow’s MCP Server and Run Your First Agentic Banking Operations

Most banking integrations treat AI agents as a liability to manage around: read-only dashboards, manual approval queues, no direct account access, etc. Meow takes the opposite position, exposing a full MCP server that lets Claude Code check balances, pull transaction history, and even stage transfers directly against a live business account.

This guide walks through that connection end to end. You’ll register Claude Code against https://mcp.meow.com, authenticate with a Meow account, and run a sequence of real financial operations with the expected output annotated at each step.

Two things to confirm before you start:

• An active Meow account with a registered business checking account
• Claude Code installed locally

What You’re Setting Up

Connecting Claude Code to Meow’s MCP server gives Claude a typed tool interface with named operations and defined inputs and outputs, rather than raw HTTP requests. A prompt like “give me all the transactions from last month” returns a structured, easy-to-read response
This tutorial registers Claude Code against the https://mcp.meow.com endpoint and authenticates through claude /mcp, which opens a browser-based OAuth grant flow. Once connected, your permissions are scoped to whatever access you grant during that flow.

The full flow from registration to first financial operation looks like this:

CLI Surface vs. OAuth Surface: Picking the Right Endpoint

Meow’s MCP server has two distinct surfaces, and confirming which one applies to your setup matters before running a command.

This tutorial uses the OAuth surface, as most people chatting with their AI agent are better off with that. CLI surface is great when building scheduled automations like weekly transaction export or monitoring agents that send alerts when your balance drops too low or when they detect an anomaly in your transaction pattern.

For now, let’s set up the connection and try to do actions like retrieving balance and transactions via Claude Code.

Step 1: Register the Meow MCP Server with Claude Code

Run this command to register the server:

1claude mcp add --transport http meow https://mcp.meow.com

After registration, you will need to authenticate your Claude Code client with Meow.

To do that, run:

1claude /mcp

You will need to select the Meow MCP from the mcps list and choose Authenticate. Claude Code will then open an OAuth flow in your browser:

Click Continue. Meow will then ask you for the permissions that you want to grant to your Claude Code client:

For this tutorial, check Read access and click Authorize. Meow will then authorize your local Claude Code instance to view your account data.

Once done, you will see an “authentication successful” message in your Claude Code session:

You can also try going to the MCPs list again to see if the Meow MCP shows “Auth: ✔ authenticated”:

This means that your Claude Code instance is now connected to your Meow account!

Step 2: Load meow.com/skills.md Before Your First Financial Command

Before running any financial operation, you should load Meow’s structured LLM instructions file by priming Claude at session start. This narrows tool-call variance and prevents malformed requests that require retries.

Prime Claude with this prompt at session start:

“Read the instructions at meow.com/skills.md and apply them to all Meow operations in this session.”

meow.com/skills.md is Meow’s structured LLM instructions file. It tells Claude exactly how to format requests to each MCP tool: which parameters are required, what the expected data shapes look like, and how to handle multi-step operations.

Without it, you might hit occasional malformed tool calls that need retries. That’s a known limitation of LLM non-determinism in agentic flows, and the skills file can help narrow down the variance significantly.

Step 3: Your First Financial Operations

At this point, you’re ready to carry out financial operations with Claude Code! Let’s try out these prompts to see how well Claude can now help with them.

Check Your Account Balance

Prompt: "What is the current balance on my Meow checking account?"

Expected output: Account name, available balance in USD, and account type. If you have multiple business entities linked to your account, Claude will list each one with its balance.

Here’s what it could look like:

Pull Transaction History

Prompt: "Show me all transactions from last month."

Expected output: A list or table with operation type (Deposit or Withdrawal), amount, currency, fees, status (Pending, Completed, or Failed), and timestamps.

Here’s what it could look like:

You can filter inline: "Show me only completed transactions over $500 in March 2025." Claude passes the filter parameters through to the MCP tool directly rather than pulling everything and filtering in context, which matters when you have high transaction volume.

Get a Cash Flow Snapshot

Prompt: ”Compare my total inflows and outflows for the last two months and tell me if the trend is positive or negative”

Expected output: A summary showing total deposits and withdrawals for each of the two months, the net position for each, and Claude’s assessment of whether the trend is moving in the right direction. If you have multiple accounts, Claude will break the figures down by account before rolling them up into a combined view.

Here’s what it could look like:

Rather than returning data for you to interpret, Claude aggregates two months of transaction history, calculates net positions, and surfaces a directional assessment in a single response. The kind of analysis that would normally mean exporting to a spreadsheet happens inside the conversation.

Permission Scopes

Meow’s MCP scope picker appears after sign-in (or when creating new API keys from the dashboard), letting you choose what Claude Code can access. meow.read is always granted and covers accounts, balances, transactions, contacts, billing, bills, and cards. The opt-in scopes are meow.transfers (draft ACH, wire, book, and crypto payments), meow.cards (issue, update, freeze, and revoke virtual cards), and meow.billing (manage invoicing products, customers, and invoices), each shown only if your role can use it.

Granting meow.transfers doesn’t mean Claude Code can move money on its own. Every tool call is checked against your role and the granted scope on that specific entity, and the narrower of the two wins. Transfers created through MCP land in a pending-approval state and execute only after a human approves them on the Meow dashboard.

What to Automate Next

You have a live Claude Code and Meow MCP session. Go to meow.com/mcp, scan the full list of available MCP tools beyond what this tutorial covered (invoicing, bill pay, corporate card management), and identify one workflow you currently handle manually.

Good starting points:

• A weekly transaction export that feeds your bookkeeping tool
• Contractor invoice payments on a recurring schedule
• A cash flow monitoring agent that pings you when available balance drops below a threshold you define

Pick the one you’d actually use, write a Claude Code prompt for it, and run it while the session is still warm.

For multi-agent architectures, generate a separate scoped API key per agent with independent permission levels. An agent reviewing incoming invoices shouldn’t share credentials with the agent initiating ACH transfers. Meow supports this natively. Each agent holds its own key with its own permission boundary, and you can revoke any individual key instantly from the dashboard with no effect on the others.

Bookmark meow.com/skills.md as an ongoing reference. It updates as new tools are added to the MCP server.

Frequently Asked Questions

How is connecting Claude Code to an MCP server different from calling a REST API directly?
When Claude Code connects via MCP, it gets a typed tool interface with named operations and defined input/output schemas. It calls tools rather than constructing HTTP requests, which means structured, schema-bound responses and far less prompt engineering required to handle edge cases.

Which endpoint should I use: https://mcp.meow.com or https://mcp.meow.com/cli?
If you’re connecting Claude Code interactively (which this tutorial covers), use https://mcp.meow.com. That’s the OAuth surface, and it covers all entities your login can reach. The /cli endpoint is for coding agents, scheduled automations, and agent-led account signup, authenticated with a Bearer API key rather than an OAuth grant.

What does the OAuth permission picker control?
After you authenticate through claude /mcp, Meow shows you a permission picker. Read access covers accounts, balances, and transaction history. Invoicing and billing covers managing invoices, products, and customers. You can also grant transfer access to stage ACH, wire, and book payments. Grant only what you need for the work you’re doing and scope further from there.

Why load meow.com/skills.md before running financial commands?
The skills file is Meow’s structured LLM instructions file. It tells Claude the exact parameter names, data shapes, and multi-step sequencing each MCP tool expects. Without it, you’ll occasionally hit malformed tool calls that need retries. Loading it at session start is the most effective way to reduce that variance.

What happens if I prompt Claude to do something my scopes don’t cover?
Claude will tell you the operation isn’t available rather than failing silently. If you ask for something that requires transfer permissions and you’ve only granted read access, the MCP server returns an insufficient scope error, and Claude surfaces that in the conversation. You can re-authenticate through claude /mcp to update your granted scopes without re-registering the server.

Can I ask Claude to filter transaction history without pulling everything first?
Yes. Claude passes filter parameters (date range, amount threshold, status) directly to the MCP tool rather than retrieving all transactions and filtering in context. That matters when you have high transaction volume and want to avoid unnecessary data retrieval.

Can I run multiple Claude Code agents against the same Meow account?
Yes. Generate a separate scoped API key for each agent and assign only the permissions that agent needs. An agent reviewing incoming invoices shouldn’t share credentials with the agent initiating ACH transfers. You can revoke any individual key instantly from the Meow dashboard with no effect on other active agents.

Is Meow’s MCP integration compliant with financial data security requirements?
PII never touches LLM providers. Meow’s Plaid KYC layer handles identity verification, and financial data stays within Meow’s infrastructure. Meow is SOC 2 compliant (report available at trust.meow.com) and accounts are held at FDIC-insured partner banks: Cross River Bank and Grasshopper Bank, N.A.

Connect your first agent to a live business account and explore the full Meow MCP toolset at meow.com/mcp