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.
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.
Google Merchant Accounts tool surface.
The following managed tool groups are exposed by this integration. Each item is surfaced as tool metadata so agents can discover safe actions and build reliable workflows.
- Google Merchant Accounts tools
- Manage Merchant Center accounts, users, terms of service, online returns, programs, and account relationships.
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.