Merchant Center MCP for catalog action

A Google Merchant Center MCP server connects Merchant Center data and operations to AI clients through the Model Context Protocol. With Markifact, Claude, ChatGPT, Cursor, or another compatible client can analyze catalog health and perform controlled product, data source, inventory, promotion, and account changes.

Yes. Google announced an alpha Merchant API MCP service in May 2026. Google describes it as authorized access to Merchant Center data and insights with a focus on read-only use.

Yes. Markifact's Merchant Center MCP is designed for full read and write workflows. It can inspect products and performance, then create data sources, insert or update products, manage inventory and promotions, and perform other Merchant API mutations after explicit approval.

Google's announced alpha focuses on read-only data and insights. Markifact adds managed write operations across product inputs, data sources, inventory, promotions, policies, conversions, and account configuration, with a human approval checkpoint before execution.

Yes. You can create, list, inspect, update, fetch, and delete supported data sources, including primary and supplemental product sources, inventory sources, and promotion sources. Google applies API-specific restrictions to certain source types.

Yes. Markifact supports the full product input lifecycle: insert new offers, patch selected attributes such as price or availability, refresh complete product records, add supplemental attributes, and delete products that should no longer be submitted.

Yes. The AI can list processed products, inspect approval and destination status, group item issues, and connect diagnostic findings with traffic and conversion data before preparing a fix.

Yes. Markifact can read and write local or regional inventory data, including store-level and region-level price and availability, subject to the Merchant Center programs and data sources enabled for the account.

Yes. It can create the required promotion data source, insert or update promotions, retrieve their review status, and manage promotion details. Google still reviews promotions against its eligibility and policy requirements.

Yes. Markifact's write scope includes commerce configuration such as supported shipping services and return policies, alongside products, inventory, promotions, conversion sources, and account settings.

Yes. Markifact can select and reuse multiple merchant accounts, including agency and advanced-account structures, so teams can compare catalog health and apply approved operations at the correct account level.

No. Read operations can run immediately, but every mutation stops at a Markifact approval request. You can inspect the selected account, data source, product identifiers, fields, and values before the operation executes.

Not when you connect through Markifact. A self-hosted MCP normally requires a Google Cloud project, Merchant API enablement, OAuth credentials, token storage, deployment, and ongoing API maintenance. Markifact provides the hosted connection.

Yes. Community options include gmc-mcp, a Python project built on Merchant API v1 with broad tool coverage. Open-source servers can be powerful, but your team owns credential security, hosting, permissions, upgrades, audit controls, and production safeguards.