Back to MCP Servers

Cash App MCP Server

No official Cash App MCP server exists. Cash App's consumer features (P2P, banking, investing) have no public API. Only Cash App Pay merchant APIs are exposed.

Payments by Block, Inc. (no official MCP server) None active
Overview

No official Cash App MCP server is published by Block, Inc. As of this writing, Cash App does not maintain a Model Context Protocol server, and there is no widely adopted or verifiable community implementation. The Cash App organization on GitHub (github.com/cashapp) hosts open-source projects like Misk, Paparazzi, Zipline, and the Cash App Pay mobile SDKs, but none of these expose MCP endpoints.

Cash App's public developer surface is limited to the Cash App Pay Partner API at developers.cash.app. This API is designed for merchants and platforms to accept payments from Cash App users at checkout, not for programmatic access to consumer Cash App features. There is no public API for sending peer-to-peer payments, querying balances, moving money in or out of the Cash App banking product, or trading Bitcoin or stocks through Cash App Investing. Any agent workflow targeting those consumer features is not possible through official channels.

Block (Cash App's parent company) has been a prominent MCP adopter internally through its open-source agent framework "Goose," and Block publishes a Square MCP server for the Square seller platform (separate product). If you need MCP access to a Block-owned payments product, the Square MCP server is the only official option available.

Setup Guide

No official MCP server available

There is no npm install or remote URL to point an MCP client at for Cash App. The following are accurate as of this writing:

  • Cash App organization on GitHub (github.com/cashapp): No repository named mcp, cash-app-mcp, or similar exists across the 57 public repositories.
  • Cash App developer portal (developers.cash.app): Documents only the Cash App Pay Partner API (Network API, Management API) for merchant payment acceptance. No MCP integration is referenced.
  • Consumer Cash App features (P2P send/receive, Cash App Card, savings, Bitcoin, stocks): No public API exists, so no MCP server can be built against them without violating Cash App's terms of service.

If you need payments MCP access

For payments-related MCP servers from Block-owned products, use the Square MCP server instead:

{
  "mcpServers": {
    "square": {
      "command": "npx",
      "args": ["-y", "square-mcp-server"],
      "env": {
        "ACCESS_TOKEN": "your-square-access-token",
        "SANDBOX": "true"
      }
    }
  }
}

Verify the latest install command at https://github.com/square/square-mcp-server and the Square developer docs at https://developer.squareup.com/docs/mcp.

If you must build a Cash App Pay integration

You can build a custom MCP server that wraps the Cash App Pay Partner API (merchant-side checkout flows). This requires:

  • A Cash App Pay partner account
  • OAuth credentials from developers.cash.app
  • Implementing MCP tools around the Network API endpoints documented at https://developers.cash.app

This would only cover merchant checkout, not consumer P2P, banking, or investing.

Use Cases
  • No supported use cases. Cash App does not provide an MCP server or a consumer API that would enable agentic workflows against P2P payments, the Cash App Card, savings, Bitcoin trading, or Cash App Investing stock trades.
  • Merchant payment acceptance (custom build required): A developer could build a non-official MCP server wrapping the Cash App Pay Partner API to let agents create Cash App Pay checkout sessions inside a merchant flow.
  • For Block-owned payments via MCP: Use the official Square MCP server (github.com/square/square-mcp-server) for catalog, orders, customers, and payments on the Square seller platform.
  • For general payments MCP coverage: Stripe, PayPal, and Cashfree all publish MCP servers that handle payment intents, payouts, refunds, and customer management.
Example Prompts
  • (Not applicable, no Cash App MCP server exists)
  • If you build a custom Cash App Pay wrapper: "Create a Cash App Pay checkout session for $42.50 and return the redirect URL."
  • For Square MCP instead: "List my Square catalog items and update the price of the espresso SKU to $4.25."
  • For Stripe MCP instead: "Refund the most recent charge from customer cus_123 and email them a receipt."
Pros
  • N/A. There is no server to evaluate.
  • Cash App's parent company Block is an active MCP contributor, so an official server may appear in the future.
Limitations
  • No official MCP server exists. Block has not published a Cash App MCP server, and there is no verifiable community implementation in the official MCP registry or Cash App's GitHub org.
  • No consumer API. Cash App does not expose P2P, banking, Bitcoin, or stock trading through any public API, so an MCP server for the "peer-to-peer payments, banking, and investing" use case cannot be legitimately built.
  • Partner API is merchant-only. The Cash App Pay Partner API at developers.cash.app covers checkout for merchants and is not designed for consumer account access.
Alternatives
  • Square MCP Server: Official MCP server from Block for the Square seller platform. Covers catalog, orders, customers, payments.
  • Stripe MCP: Official Stripe agent toolkit with MCP support for payments, customers, products, and invoices.
  • Cashfree MCP: Official Cashfree MCP server for Payment Gateway, Payouts, and SecureID KYC APIs.