Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/markdavidgan/apple-dev-skillsInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/markdavidgan/apple-dev-skills/app-store-connect)<a href="https://agentmods.dev/mcp/markdavidgan/apple-dev-skills/app-store-connect"><img src="https://agentmods.dev/badge/mcp/markdavidgan/apple-dev-skills/app-store-connect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/markdavidgan/apple-dev-skills/app-store-connect"><img src="https://agentmods.dev/badge/mcp/markdavidgan/apple-dev-skills/app-store-connect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
app-store-connect scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"app-store-connect": {
"command": "node",
"args": [
"./src/mcp/asc/dist/index.js"
],
"env": {
"ASC_KEY_ID": "${ASC_KEY_ID}",
"ASC_ISSUER_ID": "${ASC_ISSUER_ID}",
"ASC_KEY_PATH": "${ASC_KEY_PATH}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A 9eb297420667
app-store-connect is an MCP server published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
asc-mcp
41 tools to ship an App Store release: metadata, screenshots, builds, TestFlight, IAP, submit. Runs locally from the @pofky/asc-mcp npm package. Needs 4 environment variables to run.
asc-mcp
Every App Store Connect + StoreKit 2 endpoint. 902 tools in 13 profiles, narrow to 27. Runs locally from the @erayendes/asc-mcp npm package. Needs 5 environment variables to run.
ASC-Access
Heimdall — MCP server for the Apple App Store Connect API and App Store Server API (StoreKit 2). 902 tools across 13 profiles, generated from Apple's official OpenAPI spec, plus review triage and reply drafting that runs on your own model, and confirm-bef. Runs locally from the @erayendes/asc-mcp npm package.
appstore-connect
MCP server for Apple's App Store Connect API. Manage apps, TestFlight, and more. Runs locally from the asc-mcp npm package.
app-store-connect-mcp
MCP server "app-store-connect-mcp" as configured in imfaisii/asc-mcp. Runs locally from the app-store-connect-mcp npm package.
app-store-connect
App Store Connect MCP server — manage iOS/macOS apps, TestFlight, in-app subscriptions, and App Store metadata from Cursor, Claude, or any Model Context Protocol client. Uses official App Store Connect API. Runs locally from the mcp-asc npm package. Needs 4 environment variables to run.