A Model Context Protocol (MCP) server acts as a proxy between an external service that provides context, data, or capabilities to a Large Language Model (LLM) or AI application. MCP servers connect AI applications to external systems such as databases and web services, translating their responses into a format that the AI application can understand.
Server Setup
You must enable MCP servers and set up authentication before use. For more information about using Google and Google Cloud remote MCP servers, see Google Cloud MCP servers overview.
Server Endpoints
An MCP service endpoint is the network address and communication interface (usually a URL) of the MCP server that an AI application (the Host for the MCP client) uses to establish a secure, standardized connection. It is the point of contact for the LLM to request context, call a tool, or access a resource. Google MCP endpoints can be global or regional.
The Google Pay & Wallet Developer MCP server has the following global MCP endpoint:
- https://paydeveloper.googleapis.com/mcp
MCP Tools
An MCP tool is a function or executable capability that an MCP server exposes to a LLM or AI application to perform an action in the real world.
Tools
The paydeveloper.googleapis.com MCP server has the following tools:
| MCP 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 list of all Google Pay merchant business profiles associated with the authenticated account. |
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. |
create_merchant |
Creates a new merchant with the authenticated account. You MUST ask the user to provide the required information for merchant creation. Do not call this tool until you have attempted to collect the required information for merchant creation. After the merchant is created, you MUST present the Business Console Terms of Service URL to the user and instruct them to accept it before they can perform any operations on this merchant. |
create_google_pay_integration |
Creates a Google Pay integration for a specific merchant. This operation requires the user to have accepted the Business Console Terms of Service and the Google Pay API Terms of Service. You do not need to preemptively check for these. If they have not been accepted, the tool call will fail and the error message will contain the specific Terms of Service URLs that need to be accepted. If this occurs, present the URLs to the user for acceptance, and instruct them to try again once accepted. Follow this sequence to interact with the user BEFORE calling the tool: 1. First, ask the user for the integration item (Only Web integration is supported for now). - Ask for the website URL. # - If the integration item is App integration, ask for the Android app package name. 2. Then, ask the user for the integration type: - Tell the user to choose Gateway if they use one of our supported Payment Service Providers (PSPs: https://developers.google.com/pay/api#participating-processors), otherwise choose Direct. 3. For ALL integration types (Direct or Gateway): - Tell the user to upload screenshots (1MB max) of their buyflow integrated with the Google Pay API. Their buyflow must be reviewed and approved before they're given full production access. Examples: https://developers.google.com/pay/api/web/guides/brand-guidelines#put-it-all-together. - You MUST ask the user to provide 5 supporting screenshots. Ask for them ONE BY ONE to ensure correct mapping. Use ONLY the user-friendly enum descriptions when asking. 4. If the integration type is Direct: - You MUST ALSO ask the user to provide the PCI attestation document in PDF format. Use ONLY the user-friendly enum description when asking. 5. For each file provided, ask the user to provide the document path or name if in the current directory. Map it to the correct DocumentType and set the name field to a descriptive name (e.g., item_selection.png or pci_attestation.pdf) in the request. Do not call this tool until you have attempted to collect the required documents for the selected integration type. |
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. |
Get MCP tool specifications
To get the MCP tool specifications for all tools in an MCP server, use the tools/list method. The following example demonstrates how to use curl to list all tools and their specifications currently available within the MCP server.
| Curl Request |
|---|
curl --location 'https://paydeveloper.googleapis.com/mcp' \ --header 'content-type: application/json' \ --header 'accept: application/json, text/event-stream' \ --data '{ "method": "tools/list", "jsonrpc": "2.0", "id": 1 }' |