Google Merchant Reports integration for AI agents.
Google Merchant Reports 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 Reports 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 Reports actions, managed and audited.
Your user connects Google Merchant Reports once; your agent can then search Merchant Center reporting data for commerce performance, product, and account insights — 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 Reports 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.
Supported Google Merchant Reports tools.
1 tools are generated from the published Google Merchant Reports catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 1 tools. All published catalog entries are included in this page's server-rendered HTML.
- Merchantapi Accounts Reports Search
- Retrieves a report defined by a search query. The response might contain fewer rows than specified by `page_size`. Rely on `next_page_token` to determine if there are more rows to be requested.
- accounts
Google Merchant Reports integration, answered
- How do AI agents use Google Merchant Reports through Open Connector?
- Your user connects Google Merchant Reports once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Merchant Reports tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Merchant Reports MCP server?
- Yes. Open Connector can serve Google Merchant Reports as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Merchant Reports actions with credentials injected server-side.
- Where do Google Merchant Reports 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 Reports — keep the keys.
Open source, self-hostable, with Google Merchant Reports credentials that never leave your infrastructure. Run it from source today.