How do AI agents use Google Merchant Accounts through Open Connector?

Your user connects Google Merchant Accounts once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Merchant Accounts tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Google Merchant Accounts MCP server?

Yes. Open Connector can serve Google Merchant Accounts as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Merchant Accounts actions with credentials injected server-side.

Where do Google Merchant Accounts credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Google Merchant Accounts integration

Google Merchant Accounts integration for AI agents.

Google Merchant Accounts integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Merchant Accounts tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Google Merchant Accounts actions, managed and audited.

Your user connects Google Merchant Accounts once; your agent can then manage Merchant Center accounts, users, terms of service, online returns, programs, and account relationships — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Google Merchant Accounts access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Google Merchant Accounts tools.

43 tools are generated from the published Google Merchant Accounts catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 43 tools. All published catalog entries are included in this page's server-rendered HTML.

Merchantapi Accounts CreateAndConfigure: Creates a Merchant Center account with additional configuration. Adds the user that makes the request as an admin for the new account.; accounts
Merchantapi Accounts CreateTestAccount: Creates a Merchant Center test account. Test accounts are intended for development and testing purposes, such as validating API integrations or new feature behavior. Key characteristics and limitations of test accounts: - Immutable Type: A test account cannot be converted into a regular (live) Merchant Center account. Likewise, a regular account cannot be converted into a test account. - Non-Serving Products: Any products, offers, or data created within a test account will not be published or made visible to end-users on any Google surfaces. They are strictly for testing environments. - Separate Environment: Test accounts operate in a sandbox-like manner, isolated from live serving and real user traffic.; accounts
Merchantapi Accounts DeveloperRegistration GetAccountForGcpRegistration: Retrieves the merchant account that the calling GCP is registered with.; accounts
Merchantapi Accounts DeveloperRegistration RegisterGcp: Registers the GCP used for the API call to the shopping account passed in the request. Will create a user with an "API developer" and add the "developer_email" as a contact with "API notifications" email preference on. Restrictions: * The caller account must be authenticated and must not impersonate another account at registration time. Registering for subaccounts is not supported if the caller account is authenticated with the parent or the managing advanced account. * The caller account must have a [verified website](https://support.google.com/merchants/answer/11586344) in Merchant Center. * [Test accounts](https://developers.google.com/merchant/api/guides/accounts/test-accounts) are not eligible for registration.; accounts
Merchantapi Accounts DeveloperRegistration UnregisterGcp: Unregister the calling GCP from the calling shopping account. Note that the GCP will still be able to access the API for at most 1 day from the unregister succussful call.; accounts
Merchantapi Accounts GbpAccounts LinkGbpAccount: Link the specified merchant to a GBP account for all countries. To run this method, you must have admin access to the Merchant Center account. If you don't have admin access, the request fails with the error message `User is not an administrator of account {ACCOUNT_ID}`.; accounts
Merchantapi Accounts GbpAccounts List: List the GBP accounts for a given merchant.; accounts
Merchantapi Accounts Homepage Claim: Claims a store's homepage. Executing this method requires admin access. If the homepage is already claimed, this will recheck the verification (unless the business is exempted from claiming, which also exempts from verification) and return a successful response. If ownership can no longer be verified, it will return an error, but it won't clear the claim. In case of failure, a canonical error message is returned: * PERMISSION_DENIED: User doesn't have the necessary permissions on this Merchant Center account. * FAILED_PRECONDITION: - The account is not a Merchant Center account. - Merchant Center account doesn't have a homepage. - Claiming failed (in this case the error message contains more details).; accounts
Merchantapi Accounts Homepage GetHomepage: Retrieves a store's homepage.; accounts
Merchantapi Accounts Homepage Unclaim: Unclaims a store's homepage. Executing this method requires admin access.; accounts
Merchantapi Accounts Homepage UpdateHomepage: Updates a store's homepage. Executing this method requires admin access.; accounts
Merchantapi Accounts Issues List: Lists all account issues of a Merchant Center account. When called on a multi-client account, this method only returns issues belonging to that account, not its sub-accounts. To retrieve issues for sub-accounts, you must first call the accounts.listSubaccounts method to obtain a list of sub-accounts, and then call `accounts.issues.list` for each sub-account individually.; accounts
Merchantapi Accounts List: Note: For the `accounts.list` method, quota and limits usage are charged for each user, and not for the Merchant Center ID or the advanced account ID. To list several sub-accounts, you should use the `accounts.listSubaccounts` method, which is more suitable for advanced accounts use case.; accounts
Merchantapi Accounts ListSubaccounts: List all sub-accounts for a given advanced account. This is a convenience wrapper for the more powerful `accounts.list` method. This method will produce the same results as calling `ListsAccounts` with the following filter: `relationship(providerId={parent} AND service(type="ACCOUNT_AGGREGATION"))`; accounts
Merchantapi Accounts OmnichannelSettings Create: Create the omnichannel settings for a given merchant.; accounts
Merchantapi Accounts OmnichannelSettings LfpProviders Find: Find the LFP provider candidates in a given country.; accounts
Merchantapi Accounts OmnichannelSettings LfpProviders LinkLfpProvider: Link the specified merchant to a LFP provider for the specified country.; accounts
Merchantapi Accounts OmnichannelSettings List: List all the omnichannel settings for a given merchant.; accounts
Merchantapi Accounts OmnichannelSettings RequestInventoryVerification: Requests inventory verification for a given merchant in a given country.; accounts
Merchantapi Accounts OnlineReturnPolicies Create: Creates a new return policy for a given business.; accounts
Merchantapi Accounts OnlineReturnPolicies List: Lists all existing return policies for a given business.; accounts
Merchantapi Accounts Programs CheckoutSettings Create: Creates `CheckoutSettings` for the given merchant.; accounts
Merchantapi Accounts Programs CheckoutSettings DeleteCheckoutSettings: Deletes `CheckoutSettings` and unenrolls merchant from `Checkout` program.; accounts
Merchantapi Accounts Programs Disable: Disable participation in the specified program for the account.; accounts
Merchantapi Accounts Programs Enable: Enable participation in the specified program for the account.; accounts
Merchantapi Accounts Programs List: Retrieves all programs for the account.; accounts
Merchantapi Accounts Regions BatchCreate: Creates one or more regions in your Merchant Center account. Executing this method requires admin access.; accounts
Merchantapi Accounts Regions BatchDelete: Deletes multiple regions by name from your Merchant Center account. Executing this method requires admin access.; accounts
Merchantapi Accounts Regions BatchUpdate: Updates one or more regions in your Merchant Center account. Executing this method requires admin access.; accounts
Merchantapi Accounts Regions Create: Creates a region definition in your Merchant Center account. Executing this method requires admin access.; accounts
Merchantapi Accounts Regions List: Lists the regions in your Merchant Center account.; accounts
Merchantapi Accounts Relationships List: List account relationships for the specified account.; accounts
Merchantapi Accounts Services Approve: Approve an account service proposal.; accounts
Merchantapi Accounts Services List: List account services for the specified accounts. Supports filtering.; accounts
Merchantapi Accounts Services Propose: Propose an account service.; accounts
Merchantapi Accounts Services Reject: Reject an account service (both proposed and approve services can be rejected).; accounts
Merchantapi Accounts ShippingSettings Insert: Replace the shipping setting of a business with the request shipping setting. Executing this method requires admin access.; accounts
Merchantapi Accounts TermsOfServiceAgreementStates RetrieveForApplication: Retrieves the state of the agreement for the application terms of service. Application terms of service covers permissions related to the usage of data provided through Merchant Center, CSS Center, Manufacturer Center, and more.; accounts
Merchantapi Accounts Users Create: Creates a Merchant Center account user. Executing this method requires admin access.; accounts
Merchantapi Accounts Users List: Lists all users of a Merchant Center account.; accounts
Merchantapi Accounts Users Me VerifySelf: Updates the user that is represented by the caller from pending to verified.; accounts
Merchantapi TermsOfService Accept: Accepts a `TermsOfService`. Executing this method requires admin access.; termsofservice
Merchantapi TermsOfService RetrieveLatest: Retrieves the latest version of the `TermsOfService` for a given `kind` and `region_code`.; termsofservice

FAQ

Google Merchant Accounts integration, answered

How do AI agents use Google Merchant Accounts through Open Connector?: Your user connects Google Merchant Accounts once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Merchant Accounts tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Google Merchant Accounts MCP server?: Yes. Open Connector can serve Google Merchant Accounts as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Merchant Accounts actions with credentials injected server-side.
Where do Google Merchant Accounts credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Google Merchant Accounts — keep the keys.

Open source, self-hostable, with Google Merchant Accounts credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →