Microsoft App Store MCP. Manage your app's entire publishing lifecycle.
Microsoft App Store MCP handles your entire app lifecycle management within the Microsoft ecosystem. Use it to monitor submission progress, manage add-ons, and coordinate package flights for beta testing or staged rollouts. It gives your AI client real-time visibility into everything registered under your developer account.
Give Claude and any AI agent real-world access
List all applications registered in your developer account.
Monitor the current status and details of any pending or completed app submissions.
List and retrieve metadata for in-app products associated with an application.
Get details on package flights used for beta testing or staged rollouts.
Ask an AI about this
Waiting for input…
What AI agents can do with Microsoft App Store: 8 Tools for Publishing Management
Use these eight tools to pull granular data on applications, submissions, add-ons, and package flight details from your Microsoft Store account.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Microsoft App Store MCPGet Addon
Get details for a specific add-on
Get Application
Get details for a specific application
Get Flight
Get details for a specific package flight
Get Submission
Get details for a specific submission
List Addons
List add-ons for an application
List Applications
List all applications in your Microsoft Store account
List Flights
List package flights for an application
List Submissions
List submissions for an application
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Microsoft App Store, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Microsoft Store. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The headache of checking app distribution status
Right now, if you want to know what happened with a recent update, you have to log into the developer dashboard. Then you navigate through submission tabs, find the ID, and wait for the page to load just to see if it says 'Pending' or 'Approved.' It’s slow, manual clicking, and you always lose context.
With this MCP, you simply ask your agent about a specific app's status. You get immediate access to list_applications and then use list_submissions to pull the current data without opening a single browser tab. The information comes right back to your workflow.
Get clear visibility with Microsoft App Store MCP
The tedious process of checking add-on details, verifying package flight statuses, or listing all registered apps is gone. You don't have to manually cross-reference IDs across three different tabs.
Now you can get a complete picture of your entire store presence by combining list_applications with list_addons and list_flights in one conversational flow.
What Microsoft App Store MCP does for your AI
Managing an application across multiple releases is a pain. You need constant updates on submissions, in-app products, and rollout stages—stuff that used to require jumping between dozens of dashboards. This MCP connects your development workflow directly to the Microsoft Store Submission API. It lets you check every detail about your apps, from listing all registered applications to viewing metadata for add-ons.
Need to know if a beta test package is ready? You can view those flights too. When connected via Vinkius, this tool gives your AI client immediate control over your entire store presence, making the whole publishing process visible and actionable right within your chat or IDE.
019d75d4-68ca-7371-9b13-82fb51606fd6 How to set up Microsoft App Store MCP
The bottom line is you don't have to log into developer portals; your AI client just talks directly to the store data.
Subscribe to this MCP and provide your Azure Tenant ID, Client ID, and Client Secret credentials.
Your AI client authenticates with the Microsoft Store Submission API using those credentials.
You prompt your agent to perform a specific task, like listing applications or checking submission statuses.
Who uses Microsoft App Store MCP
This MCP is for developers and product managers who own apps distributed via the Microsoft Store. If you spend time manually checking submission dashboards, this is for you. It eliminates the context switching between developer portals and your actual work.
Automating release pipelines by ensuring that package flights are correctly configured before a production push.
Keeping track of the submission status and required metadata for new add-ons across multiple apps simultaneously.
Verifying that all dependencies, including listing applications and checking package flights, are correctly registered before a major deployment.
Benefits of connecting Microsoft App Store MCP
Eliminate dashboard hopping. Instead of logging into the developer portal to check submissions, you simply ask your agent for a list of submissions or use get_submission to confirm status instantly.
Keep track of everything in one place. Use list_applications to see all apps registered and then target specific ones using get_application details without leaving your chat window.
Coordinate controlled rollouts easily. You can view package flights with list_flights, letting you manage beta testing stages without manual checks for each rollout group.
Manage in-app revenue streams. Use list_addons to see all available add-ons and get_addon to check the specific metadata needed for product teams.
Get a full picture of your content. Running list_applications followed by list_submissions lets you map out exactly what's pending publication across your entire portfolio.
Microsoft App Store MCP use cases
Confirming Beta Availability
A DevOps engineer needs to know if the new build is ready for internal testing. They ask their agent to run list_flights, which returns a list of package flights, allowing them to confirm that 'Internal Testing' is active before notifying QA.
Auditing App Portfolio Status
A Product Manager needs an overview of all apps and their latest submission statuses. They ask the agent to run list_applications first, then iterate through the results using list_submissions to build a comprehensive status report.
Debugging Add-on Metadata
A developer spots an incorrect price on an add-on in production. They use get_addon for the specific product ID, immediately retrieving the metadata needed to file a correction ticket without guessing IDs.
Pre-Release Check
Before launching, an architect needs assurance that all dependencies are accounted for. Running list_applications followed by listing add-ons ensures every in-app product is visible and correctly registered.
Microsoft App Store MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Assuming App Status
The developer assumes that because they updated the code, it's submitted. They wait hours and check the portal repeatedly.
Use list_submissions to proactively check the status of your submission immediately after deployment. This confirms exactly what stage the app is in.
Manual Add-on Tracking
The product team has 20 apps and manually checks each one's store page for add-ons, leading to missed updates.
Use list_applications first, then pair that with list_addons. This systematically gathers all in-app products across your entire catalogue.
When to use Microsoft App Store MCP
You should use this MCP if your job involves managing the lifecycle of published software within the Microsoft Store. Specifically, you need to check submission statuses (list_submissions), manage beta rollouts (list_flights), or audit your product offerings (list_addons). Don't use it if you only need basic API calls for general data storage; this is specialized publishing logic. If your core pain point is understanding where a piece of code is in the store pipeline, this MCP provides the precise tools needed to map out that journey.
Frequently asked questions about Microsoft App Store MCP
How do I check the status of all my Microsoft Store apps using the Microsoft App Store MCP? +
You can combine list_applications to get every app name, and then use list_submissions on each one to pull the current submission status for a comprehensive audit.
What is the difference between listing applications and getting an application's details? +
list_applications gives you a simple roster of every app ID. get_application uses that specific ID to fetch deep, rich metadata about one single app.
Can I use the Microsoft App Store MCP to track beta rollouts? +
Yes. You can view package flights using list_flights and then check details for a specific rollout with get_flight, which is critical for controlled deployments.
Does this MCP handle add-ons and their metadata? +
It does. Use list_addons to see every in-app product available for an app, or use get_addon if you only need details on one specific product ID.