App Store MCP. Manage App Submissions & Lifecycle Status
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
The Microsoft App Store MCP Server manages your entire app publishing lifecycle through the Submission API. Use this server to track application inventory, monitor submission statuses, manage in-app add-ons, and coordinate package flights for beta testing.
It gives you real-time visibility and control over every stage of getting an app live on the platform.
What your AI agents can do
Get addon
Retrieves the detailed data for a single, specific in-app add-on.
Get application
Fetches all metadata and details for one particular application ID.
Get flight
Gets the parameters used for a single, specific package flight (e.g., beta group members).
It pulls a complete list of every application ID associated with your developer account.
You check the current state (e.g., 'PendingPublication') and history for any single application submission using get_submission.
The server lists all available add-ons for a given app, including their unique identifiers and metadata.
You get the exact parameters of a staged rollout or beta test using get_flight.
This tool lists every single in-app product that belongs to a specific application ID.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Microsoft App Store MCP Server: 8 Tools for App Lifecycle Management
Use these eight tools to query specific details about applications, submissions, add-ons, and package flights in the Microsoft Store.
019d75d4get addon
Retrieves the detailed data for a single, specific in-app add-on.
019d75d4get application
Fetches all metadata and details for one particular application ID.
019d75d4get flight
Gets the parameters used for a single, specific package flight (e.g., beta group members).
019d75d4get submission
Checks the current status and details of one particular app submission.
019d75d4list addons
Generates a list of all add-ons available for a given application ID.
019d75d4list applications
Provides a full inventory and list of every app registered in your developer account.
019d75d4list flights
Generates an overview listing all package flights associated with an application ID.
019d75d4list submissions
Provides a list and status summary for multiple app submissions across your account.
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 every 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 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
This MCP Server for the Microsoft App Store lets your agent handle your whole app publishing mess. It’s built around the official Microsoft Store Submission API, giving you direct access to everything related to getting an app live on that platform. You'll use this server to manage your entire application inventory, track submissions from start to finish, sort out in-app extras, and even coordinate beta test rollouts.
When you connect it through Vinkius, your AI client gets real visibility and control over every single stage of the process.
If you need a full picture of what apps you've got registered, start with list_applications. It spits out a complete inventory list of every application ID under your developer account. For deeper info on any specific app—like its version details or general metadata—you run get_application and get all those juicy details for that one ID.
When it comes to getting an app published, you need to know where things stand. To check the status of multiple apps at once, use list_submissions; this gives you a quick summary list and status report across your account. If you only care about one specific submission—maybe you wanna see if it's 'PendingPublication' or if it got rejected—you run get_submission to check its current state and full history.
Handling the extras is just as important. You can first use list_addons to get a list of all in-app products tied to a specific app ID. Then, if you need the deep dive on one particular product—like figuring out its exact price or unique identifier—you run get_addon and pull the detailed data for that single add-on.
For coordinating beta testing, you've got two tools. To see all the package flights associated with an app ID, you use list_flights, which gives you a high-level overview. If you wanna know the exact parameters of one specific staged rollout or beta test—like who exactly is in that beta group—you run get_flight to pull those precise details.
Essentially, this server lets your agent read and manage all these pieces: it pulls every app ID list (list_applications), tracks submission status for singles and groups (get_submission, list_submissions), manages the in-app product catalog (list_addons, get_addon), and handles staged rollout details (list_flights, get_flight). You're staying in control of your entire app lifecycle right from your agent.
How App Store MCP Works
- 1 First, subscribe to the server and provide your required credentials: Azure Tenant ID, Client ID, and Client Secret.
- 2 Next, prompt your AI client (e.g., 'List all apps for deployment') so it knows which specific tool (
list_applications) to call. - 3 The system executes the API call against Microsoft's endpoints and returns structured data (like a list of IDs or status codes) directly to your agent.
The bottom line is: you give your AI client credentials, it calls the right function, and you get clean, structured store data back—no dashboard clicking required.
Who Is App Store MCP For?
App Release Managers and Technical Program Managers. If you spend time cross-referencing submission dashboards or manually tracking which beta group got what build, this is for you. You're the person who needs a single source of truth about app deployment status across multiple environments.
They use list_applications to verify that all planned apps are registered and check add-on availability via list_addons before a major launch.
They rely on the server to track build versions; they run get_submission or list_submissions to confirm if a deployment passed QA and is ready for staging.
When writing release notes, they use this tool to pull specific metadata about add-ons (get_addon) or package flight details (list_flights) directly into documentation drafts.
What Changes When You Connect
- Instant Inventory: Use
list_applicationsto see every app ID on file immediately. You don't have to navigate through multiple developer dashboards just to confirm existence. - Pinpoint Submission Status: Instead of guessing, run
get_submissionwith an ID. You get the exact status (e.g., 'Rejected,' 'Pending') and the reason right away. - Control Rollouts: Need to know who's testing what? Use
list_flightsorget_flightto see exactly which beta groups are getting access, preventing accidental public release. - Add-on Verification: When an app relies on paid add-ons, use
list_addonsandget_addon. This confirms the metadata is correct before you point your users to it. - Bulk Tracking: Use
list_submissionsto get a status summary for 10 or 20 apps in one go. It's much faster than checking them one by one.
Real-World Use Cases
The App Launch Checklist
A PM needs to verify all components are ready before launch. They ask their agent: 'List my apps and check the submission status for all of them.' The agent runs list_applications then loops through, calling get_submission for each one. It returns a clean list showing which apps passed QA and need final approval.
Debugging a Beta Group Access Issue
A developer reports that certain users can't access the newest build. They use their agent to call list_flights for the affected app, identifying the specific flight ID and checking its parameters with get_flight. This immediately pinpoints if the wrong user group was included in the rollout.
Audit of In-App Purchases
The finance team needs to audit all paid content. They instruct their agent to use list_addons for a specific app ID. This returns every add-on name and metadata, allowing them to confirm pricing structure consistency across the board.
Checking for Orphaned Content
A developer suspects an old add-on is still listed but unused. They run list_addons against the app ID in question and then use get_addon on suspicious entries to confirm if the metadata is stale or needs removal.
The Tradeoffs
Trying to list everything at once
Asking the agent, 'Give me all my apps, their submissions, and add-ons.' This prompt lacks necessary IDs and is too broad for the API.
→
Break it into steps. First: Use list_applications to get a list of 5 app IDs. Then: For each ID, run get_submission (for status) AND list_addons (for inventory). This structured approach is reliable.
Using the wrong tool for listing
The user calls get_application when they actually need a full list of apps. The call fails because it requires one specific ID.
→
If you want all IDs, use list_applications. If you only know the ID and just want details on that single app, then use get_application.
Ignoring the submission status flow
Assuming an app is live because it was submitted. The user doesn't check if the required 'Approval' step passed.
→
Always follow up a submission attempt by calling get_submission to validate the current state. Don't assume success until you see 'Approved'.
When It Fits, When It Doesn't
Use this server when your job requires granular, real-time data about the app distribution lifecycle—specifically tracking submissions, add-ons, or flight parameters. You need API access to validate a state (e.g., Is it Approved? What are the beta participants?). Don't use this if you just need general project planning or task management; those require different tools entirely.
Do NOT use this server if your goal is simply drafting release notes or communicating high-level status updates to stakeholders—that requires a communication platform. Only run these calls when you need verifiable, machine-readable data from the Microsoft Store itself.
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 INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Tracking app submission status shouldn't require 4 different dashboards.
Right now, if your team needs to know if 'TaskMaster v2.0' is ready for publication, you have to log into the developer portal, click on the app, find the submissions tab, and then maybe check a separate flight status dashboard. It’s clicking through five different pages just to get one confirmation.
With this MCP server, your AI agent handles it. You ask: 'What's the status of TaskMaster v2.0?' The agent calls `get_submission`. It instantly returns the current state and any required actions—all in a clean block of text. No dashboard hopping.
Microsoft App Store MCP Server: Know exactly what you're rolling out.
Manual rollouts are messy. You have to manually track which specific build ID was assigned to the 'internal testing' flight and then cross-reference that against the target user group list. It’s a spreadsheet nightmare, prone to human error every time.
Now, you let your agent run `list_flights`. It shows you all active package flights for an app instantly. You can verify which users are in scope or confirm if the flight parameters match the current deployment phase. The data is immediate and verifiable.
Common Questions About App Store MCP
How do I check the status of a specific build with get_submission? +
Pass the submission ID to get_submission. This tool immediately returns the current state, including if it's 'PendingPublication,' and provides any rejection reasons if needed.
What is the difference between list_applications and get_application? +
list_applications gives you an inventory of every app ID on your account. get_application requires a specific app ID and returns all detailed metadata for only that one application.
How do I list all the paid add-ons for an app? Use list_addons. +
Calling list_addons with an App ID gives you a complete index of every in-app purchase. You can then use get_addon on any entry to pull specific metadata like price or description.
Can I see all my submission attempts at once? Use list_submissions. +
list_submissions provides an overview of multiple submissions. This is better than checking one by one, giving you a quick status summary across several deployments.
How do I use list_flights to see which packages are ready for beta testing? +
Use list_flights. It lists all package flights associated with an application, showing exactly what version is currently in staging or available for limited beta rollout. This helps coordinate your release plan before a full launch.
What information does calling get_application provide beyond just the name and ID? +
get_application returns comprehensive metadata for that specific application. You'll find things like version history, developer notes, and all core identifiers you need to manage submissions or view package flights later.
If I know an Add-on's ID, how can I use get_addon to check its specific metadata? +
Just provide the unique Add-on ID to get_addon. This returns precise details about that single product—including pricing tiers and associated content—without forcing you to list every add-on available.
What credentials must my agent use before I can run any tool like list_applications? +
You need your Azure Tenant ID, Client ID, and Client Secret. The server uses these three credentials to authenticate with the Microsoft Store Submission API. Ensure they are correctly entered into Vinkius for successful connection.
How do I create the Azure AD application? +
Go to Partner Center > Account settings > User management > Azure AD applications to associate an application and generate a secret.
Which permissions are required? +
The application must be associated with your Partner Center account and granted the 'Manager' or 'Developer' role.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
PDF.co
Parse, generate, merge, and convert PDF documents programmatically with an API that handles complex document processing tasks.
Dotcom-Monitor
Monitor website uptime, page load speed, and server health from multiple global locations with instant alert notifications.
Freshdesk
Resolve customer tickets faster with omnichannel helpdesk tools, smart automation, and self-service portals your users will love.
You might also like
FynCom
Reward customer attention with micro-payments and nano-rewards that boost survey completion and email engagement rates.
Exa
Semantic search engine built for AI — find conceptually relevant web content, not just keyword matches. Powered by neural search technology.
Amplemarket
Sales automation and lead generation — manage sequences, leads, and custom signals via AI.