Xcode-Studio-MCP
kevinswintLABSCO SUMMARY
No API key at all is a small thing that removes a whole class of mistake.
Browser-only authorisation means there is no secret to paste into a config file, commit by accident, or forget to rotate. For a tool that touches store listings rather than production data that is a sensible trade — the cost is that headless use is not on the table.
What it is
AppLaunchFlow's hosted endpoint for their App Store screenshot tooling. You connect once through a browser sign-in and the agent works against your account.
What you get
The App Store screenshot workflow the product is built around.
Requirements
OAuth 2.1 authorization-code with PKCE, done in the browser on first connect. There is no API key to store anywhere.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Producing a store screenshot set
Ask for the set while working on the release, rather than moving to a separate design tool.
02
Connecting without handling a secret
Browser sign-in with PKCE means nothing sensitive lands in a config file.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 authorization-code + PKCE (browser sign-in; no API key)
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.applaunchflow.com/mcpRequirements
- OAuth 2.1 authorization-code + PKCE (browser sign-in; no API key)
