Blog Post

Marketplace blog
4 MIN READ

Bring Marketplace publishing into your agentic development workflow

Akshat_Singal's avatar
Akshat_Singal
Icon for Microsoft rankMicrosoft
Oct 05, 2026

Bringing Marketplace publishing into the development workflow can help teams connect product development and publishing activities through the tools and processes they already use. Teams build their product, then move into a different set of tools and processes to prepare, validate, and submit it. Marketplace Ingestion MCP creates an opportunity to bring those activities closer together.

With Marketplace Ingestion MCP, publishers can use natural language and AI agents to create, validate, publish, and manage offers in Microsoft Marketplace. Instead of starting by manually constructing API payloads, publishers can describe the outcome they want. An agent can then help translate that intent into the information required by the underlying publishing APIs. Publishers can also build custom workflows using the MCP, connecting repeatable publishing activities with the development processes and tools their teams already use.

The shift is straightforward: start with the publishing outcome, not the API payload.

From publishing task to agentic workflow

Marketplace Ingestion MCP is a Model Context Protocol (MCP) server that connects MCP-compatible agent tools with Partner Center APIs.

For example, a publisher can ask an agent to create a SaaS offer and identify what is required before it can be published. The agent can retrieve the appropriate schema, build the payload, validate it, and create the offer as a draft. When the publisher is ready to continue, the agent can perform supported publishing actions. Publishers remain in control through the approval settings in their MCP client. This makes Marketplace publishing a more natural part of an agentic development workflow rather than a separate process that begins after development is complete.

Four opportunities for agent-assisted publishing

Teams exploring where Marketplace Ingestion MCP fits into their development lifecycle can start with four opportunities.

1. Start with intent

Developers do not need to begin by manually assembling an API payload. They can describe the offer they want to create or the update they want to make. The agent can use Marketplace Ingestion MCP to retrieve the required schema, build the payload, and validate it before submission.

This allows the publisher to focus first on the intended outcome while the agent handles more of the translation into API-specific structures.

2. Make repeated work part of the workflow

Offer creation and updates often include steps that teams perform repeatedly. Those steps can become reusable agentic workflows and, where appropriate, be incorporated into continuous integration and continuous delivery (CI/CD) pipelines.

The question for a development team now becomes: Which publishing activities do we repeat often enough that they should become part of our development workflow?

The answer will differ across organizations, products, and release processes. Marketplace Ingestion MCP provides the building blocks teams can use to design a workflow that fits their needs.

3. Keep people in control

Agent-assisted publishing does not require handing every decision to an agent. MCP client approval settings can require publishers to review and approve tool calls before changes are submitted. Teams can use those controls to determine where automation is useful and where human review should remain part of the process.

4. Work from familiar developer tools

Marketplace Ingestion MCP works with supported MCP-compatible clients, including Visual Studio Code and GitHub Copilot CLI. This brings Marketplace publishing tasks closer to the environments where developers already build and operate their products. It also reduces the need to treat publishing as an isolated activity performed through a separate workflow.

What does this look like in practice?

Consider a fictional publisher, Contoso, that wants to bring a Microsoft 365 agent to customers.

Contoso can provide its workflow integrated with the MCP with existing marketing material and the technical manifest for the agent. Marketplace Ingestion MCP can help translate that information into the structure required to create the product in Microsoft Marketplace.

The workflow can then build on that information to create a linked SaaS offer for monetization, using the additional details required for the SaaS offer.

The publisher describes what it wants to accomplish, and the agent uses Marketplace Ingestion MCP and the publishing APIs to turn that intent into supported publishing actions.

Getting started

Marketplace Ingestion MCP is included with access to Microsoft Marketplace publishing APIs.

Before getting started, publishers need:

  • A Partner Center account with the required role
  • Access to Microsoft Marketplace publishing APIs
  • A supported MCP-compatible client, such as Visual Studio Code or GitHub Copilot CLI

The Microsoft Learn documentation covers prerequisites, installation and authentication, available tools, supported products, data handling, and an end-to-end SaaS example.

Learn more: Marketplace Ingestion MCP server - Marketplace publisher 

Bringing publishing closer to development

AI agents are becoming part of how developers build and operate software. Marketplace publishing can become part of those workflows as well. Marketplace Ingestion MCP connects natural-language intent with supported Marketplace publishing actions. It allows teams to create repeatable workflows while keeping publishers involved in reviewing and approving changes.

The result is a closer connection between building a product and bringing it to market, helping developers focus on the cloud and AI solutions that differentiate their business.

Thank you to the many teams whose collaboration brought Marketplace Ingestion MCP to publishers. Their work reflects a shared investment in helping publishers build, publish, and grow through Microsoft Marketplace.

Updated Oct 05, 2026
Version 1.0
No CommentsBe the first to comment