Google Pay & Wallet Developer MCP server

Documentation

Documentation link · transport streamable-http (JSON-RPC 2.0 over HTTPS)

Tools

• search_documentation — Searches and retrieves the most relevant, up-to-date sections from the official Google Pay and Google Wallet developer documentation and code samples.
• list_merchants — Retrieves a comprehensive list of all Google Pay merchants associated with the authenticated account. Depending on the user's role on a merchant, admins can view full detailed merchant information, while developers can only view basic merchant information.
• list_google_pay_integrations — Returns the current status and configuration details for all Google Pay integrations associated with a specific Merchant ID. It provides immediate feedback on the status of integration and document reviews. Additionally, you MUST inform the user that the integration can be created/updated in the Google Pay & Wallet Console (https://pay.google.com/business/console/).
• create_merchant — Creates a new merchant with the authenticated account. You MUST ask the user to provide the required information for merchant creation. One of the required fields is the Merchant Category Code (MCC). Since the list of MCCs is long, you may present a subset of common options, but you MUST inform the user that more options are available and they can ask for the full list (e.g. by showing "X more opt…
• list_pass_issuers — Retrieves a comprehensive list of all pass issuers registered in the Google Wallet business console associated with the authenticated user. This tool provides essential information for developers managing Wallet passes like loyalty cards, gift cards, or flights.
• list_pass_classes — Retrieves a comprehensive list of all pass classes registered in the Google Wallet business console associated with the authenticated user. This tool provides essential information for developers managing Wallet passes like loyalty cards, gift cards, or flights.
• validate_pass_jwt — Validates the JWT representation of a pass, or the unencoded JWT payload as a JSON string for a pass.
• query_merchant_performance — Retrieves high-level aggregated performance data and post-integration metrics for a specific merchant business profile.
• query_merchant_error_metrics — Retrieves detailed error metrics for a specific merchant business profile. This tool provides a granular breakdown of errors, allowing developers to pinpoint and resolve issues.
• update_merchant — Updates specific fields of an existing merchant. Supported fields include display_name, mcc, corporate_website_url, customer_support_website_url, customer_support_email, and customer_support_phone.
• list_principals — Lists the principals (users) that have access to a specific merchant. This operation requires Admin access for the merchant.
• set_principal_role — Sets the role of a principal (user) on a merchant, or adds a new principal with the specified role. The principal is sent an email invitation and must accept it before their access becomes active. This operation requires Admin access for the merchant.
• delete_principal — Deletes a principal's (user's) access to a specific merchant. This operation requires Admin access for the merchant.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/google-pay-wallet-developer-mcp-server"

curl "https://apis.io/api/v1/mcp?limit=25"