CoolMeow
English
← Back to CoolMeow

MCP

Connect your cloud ledgers to your AI tools

An AI client with remote MCP support can read and update your CoolMeow cloud ledgers. Sign in with your existing CoolMeow account, then choose the ledgers and permissions to allow.

MCP server URL
https://coolmeow.aside0.com/mcp

What you can do

Look up expenses
Search entries, categories, members and approvals. Get totals by date or category, expense splits and settlement balances.
Add and edit records
Add or update expenses and manage categories and participants. Changes go through a preview before they are written.
Manage shared ledgers
Manage invitations, approvals and share links where your role allows it. Deletion, restoration and other sensitive actions need extra permission.
Read receipt images
Clients that support images can read receipt attachments from authorized ledgers. Their image recognition determines the results.

Before you connect

A CoolMeow account and cloud ledger
Use the same account as in the app. MCP accesses cloud ledgers only; it does not upload local ledgers. If you need a cloud ledger, create one or accept an invitation in the app first.
Basic membership
The ledger owner needs an active Basic membership to create a shared cloud ledger and keep it editable. Invited members can participate for free, within their assigned roles. To buy or renew Basic, download CoolMeow and purchase it in the app. Purchases are not available on this website or through MCP.
A client with remote MCP support
The client must support Streamable HTTP and OAuth sign-in. Availability can depend on its version, plan and organization settings. AI subscriptions and model charges come from that provider; Basic does not cover them.

Download CoolMeow

Choose how to connect

All methods use the same server URL. Codex’s native OAuth connection has been verified in our test environment. The other instructions follow the clients’ official documentation, but their connections to CoolMeow have not yet been verified individually. Use a current version with remote MCP support.

CodexCLI commands
  1. With Codex CLI installed, run these commands and finish authorization in your browser.
  2. Start a new Codex session. Use /mcp to check the connection.
Codex
codex mcp add coolmeow --url https://coolmeow.aside0.com/mcp
codex mcp login coolmeow
codex mcp list

Alternatively, add [mcp_servers.coolmeow] and its url to ~/.codex/config.toml, then run codex mcp login coolmeow.

~/.codex/config.toml
[mcp_servers.coolmeow]
url = "https://coolmeow.aside0.com/mcp"
Official client documentation
ClaudeCustom connector
  1. Open Customize → Connectors → + Add → Add custom connector. Enter a name and the URL below.
  2. Choose Sign in now and Register automatically for OAuth client. Authorize, then enable it under Connectors in your conversation.
Claude
https://coolmeow.aside0.com/mcp

An organization admin may need to add the connector first. CoolMeow uses automatic registration; Claude’s published identity is not supported.

Official client documentation
CursorJSON configuration
  1. Merge this into ~/.cursor/mcp.json or your project’s .cursor/mcp.json. Keep any existing server entries.
  2. Reload Cursor, sign in for coolmeow in its MCP settings, and enable it in Agent.
Cursor
{
  "mcpServers": {
    "coolmeow": {
      "url": "https://coolmeow.aside0.com/mcp"
    }
  }
}
Official client documentation
VS CodeJSON configuration
  1. Merge this into your project’s .vscode/mcp.json. For user-wide setup, run MCP: Open User Configuration.
  2. Start coolmeow, follow the trust and sign-in prompts, and enable its tools in Agent chat.
VS Code
{
  "servers": {
    "coolmeow": {
      "type": "http",
      "url": "https://coolmeow.aside0.com/mcp"
    }
  }
}
Official client documentation

Choose ledgers and permissions

  1. Check your account

    Sign in on CoolMeow’s authorization page and check that it is the right account. Complete email verification if requested. Use one of the sign-in methods shown on the page.

  2. Choose ledgers

    No ledgers are selected by default. You can select specific ledgers. Creating a new ledger or accepting a new invitation requires explicitly allowing all ledgers you can access now and in the future.

  3. Choose access

    Read access is enough for queries. Add write access for edits, and sensitive access for actions such as deletion, invitations and public sharing. Authorization never changes your role in a ledger.

Readledger:read
Query authorized ledgers without changing them.
Writeledger:write
Preview and apply ordinary edits, subject to approval rules.
Sensitive actionsledger:sensitive
Also allow deletion, restoration, invitations and public sharing. Requires write access too.

Try a request

Show last week’s food expenses in ‘Kyoto trip’, with separate totals for each currency.

Add today’s dinner to ‘Household’: USD 120, paid by me, split equally between three people. Show me the preview and wait for my confirmation before saving.

Who still owes money in ‘Kyoto trip’? List who should pay whom.

How changes are saved

  1. Specify the ledger, amount, currency, date, payer and split. Ask the client to clarify missing details first.
  2. The client requests a preview showing the proposed changes. Check it before asking the client to proceed. Previews expire after five minutes; changes to relevant records also require a new preview.
  3. Check the execution result and the record in the app. If a request times out or the result is unclear, check the original operation’s result before trying again to avoid duplicates.

Limitations

Cloud data only
MCP cannot access offline local ledgers, your phone’s camera or microphone, notification settings, or app store purchases.
Roles and membership still apply
Read-only members cannot write, and editors do not gain owner permissions. Connecting an AI client does not bypass a read-only ledger, expired membership or approval rules.
Confirmation depends on the client
The server requires a preview before a write, but a preview is not proof of your consent. Confirmation prompts and automatic execution depend on the client. Check its tool approval settings if you want to approve each change.
AI can misunderstand a request
Check the ledger, currency, date and split. Reporting tools return separate totals by currency, without adding different currencies together. Check any explanation or conversion the AI produces itself.
No money transfers or app receipt recognition
Settlement records document payments already made; they do not send money. MCP does not use CoolMeow’s in-app receipt recognition service or its quota. Image recognition depends on the external client and its pricing.
Your client handles the returned data
Ledger records and receipt images may enter the external AI service’s context or conversation history. That service’s storage, training and deletion policies apply. You can limit access to specific ledgers and start with read access.

If something does not work

A ledger is missing
Check the signed-in account, whether the ledger is in the cloud, your active membership in it, and your selected ledgers on the authorization page. Authorize again to change the selection.
Sign-in fails or there is no connection option
Update the client and check remote MCP, OAuth and organization permissions. Choose automatic registration (DCR) when asked. CoolMeow does not support legacy HTTP+SSE or require you to enter an API key.
Disconnecting and revoking access
Disable the connection in your client. If it offers authorization revocation, use it; deleting a local configuration alone does not guarantee that server-side authorization is revoked. Contact support if no revocation option is available or you need help.
Contact support
Developer reference
Transport and authentication
Remote Streamable HTTP (POST), OAuth authorization codes, S256 PKCE and Dynamic Client Registration (DCR). No stdio executable, legacy SSE endpoint or permanent API key is provided.
Query limits
Lists return 50 items by default, up to 100 per page. Follow nextCursor for more. A filtered report covers up to 10,000 records; narrow the date range for larger ledgers.
Writes and recovery
Preview tokens last five minutes. Execute with the original preview and operationID. After a timeout, query ledger_operation before retrying. A batch of ordinary writes allows up to 20 independent actions in one ledger.

Available tools

ledger_query
Read records, reports and splits
ledger_preview
Validate changes and return a preview
ledger_execute
Apply ordinary changes
ledger_execute_sensitive
Apply separately authorized sensitive actions
ledger_operation
Look up execution receipts and recover results