Token导航 LogoToken导航

Agent Skill · 研究检索

axiom-asc-mcp(axiom ASC MCP 搜索)

axiom-asc-mcp 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

axiom-asc-mcp 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,674 个 Skill 里排第 33,416。

总安装 2,352周安装 98GitHub Stars 873下载 784核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:axiom-asc-mcp(axiom ASC MCP 搜索)
来源仓库:https://github.com/charleswiltgen/axiom
仓库路径:skills/axiom-asc-mcp
安装命令:
npx skills add https://github.com/charleswiltgen/axiom --skill axiom-asc-mcp
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/charleswiltgen/axiom --skill axiom-asc-mcp

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

通过 MCP 协议集成 App Store Connect 全流程管理。支持构建提交、TestFlight 分发和评论回复自动化。需配置 API Key 并安装 asc-mcp 命令行工具。

安装命令:npx skills add https://github.com/charleswiltgen/axiom --skill axiom-asc-mcp 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/axiom-asc-mcp

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/charleswiltgen/axiom --skill axiom-asc-mcp;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

axiom-asc-mcp 怎么安装?

在终端执行 npx skills add https://github.com/charleswiltgen/axiom --skill axiom-asc-mcp。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

axiom-asc-mcp 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

axiom-asc-mcp 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

axiom-asc-mcp 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

axiom-asc-mcp 用的人多吗?

公开数据是累计安装 2,352 次,近一周安装 98 次,下载 784 次,GitHub 873 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

axiom-asc-mcp 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
axiom-asc-mcp

axiom ASC MCP 搜索 · 本页

2,352873接触敏感数据未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

App Store Connect MCP Integration

Core principle: When asc-mcp is configured, you can manage the entire App Store Connect workflow without leaving Claude Code — submit builds, distribute to TestFlight, respond to reviews, and monitor metrics programmatically.

Setup

Install

brew install mint
mint install zelentsov-dev/asc-mcp@1.4.0

Create API Key

  1. Open App Store Connect → Users and Access → Integrations → API
  2. Generate key with Admin or App Manager role
  3. Download the .p8 file (one-time download — save it securely)
  4. Note the Key ID and Issuer ID

Add to Claude Code

claude mcp add asc-mcp \
  -e ASC_KEY_ID=YOUR_KEY_ID \
  -e ASC_ISSUER_ID=YOUR_ISSUER_ID \
  -e ASC_PRIVATE_KEY_PATH=/path/to/AuthKey.p8 \
  -- ~/.mint/bin/asc-mcp

Verify

Ask Claude to call company_current. If it returns your team name, you're connected.


Worker Filtering

asc-mcp has 25 workers (~208 tools). Loading all of them wastes context. Use --workers to load only what you need.

Presets

PresetWorkersToolsUse Case
TestFlightapps,builds,beta_groups,beta_testers~34Beta distribution
Releaseapps,builds,versions,reviews~40App Store submission
Monetizationapps,iap,subscriptions,offer_codes,pricing~55IAP and subscriptions
Full(default, all workers)~208Everything

To use a preset, add --workers when registering the server:

claude mcp add asc-mcp \
  -e ASC_KEY_ID=... \
  -e ASC_ISSUER_ID=... \
  -e ASC_PRIVATE_KEY_PATH=... \
  -- ~/.mint/bin/asc-mcp --workers apps,builds,versions,reviews

Note: company and auth workers always load regardless of --workers. When builds is enabled, build_processing and build_beta are included automatically.

Worker Selection Decision Tree

digraph workers {
    "What are you doing?" [shape=diamond];
    "TestFlight preset" [shape=box, label="--workers apps,builds,\nbeta_groups,beta_testers"];
    "Release preset" [shape=box, label="--workers apps,builds,\nversions,reviews"];
    "Monetization preset" [shape=box, label="--workers apps,iap,\nsubscriptions,offer_codes,pricing"];
    "Full (no flag)" [shape=box, label="No --workers flag\n(all 208 tools)"];

    "What are you doing?" -> "TestFlight preset" [label="distributing beta builds"];
    "What are you doing?" -> "Release preset" [label="submitting to App Store"];
    "What are you doing?" -> "Monetization preset" [label="managing IAP/subscriptions"];
    "What are you doing?" -> "Full (no flag)" [label="multiple tasks or unsure"];
}

Workflow: Release Pipeline

Submit a new version to the App Store.

1. apps_search(query: "MyApp")           → get app ID
2. builds_list(appId, limit: 5)          → find latest processed build
3. app_versions_create(appId, platform: "IOS", versionString: "2.1.0")
4. app_versions_attach_build(versionId, buildId)
5. app_versions_set_review_details(versionId, { contactEmail, notes, ... })
6. app_versions_submit_for_review(versionId)
7. (After approval) app_versions_create_phased_release(versionId)

Before step 3: Version string must not already exist. Check with app_versions_list.

Before step 4: Build must be in VALID processing state. Check with builds_get_processing_state.

Before step 6: Version must be in PREPARE_FOR_SUBMISSION state. Attaching a build and setting review details are prerequisites.


Workflow: TestFlight Distribution

Distribute a build to beta testers.

1. apps_search(query: "MyApp")           → get app ID
2. builds_list(appId, limit: 5)          → find latest build
3. builds_set_beta_localization(buildId, locale: "en-US", whatsNew: "Bug fixes")
4. beta_groups_list(appId)               → find or create group
   OR beta_groups_create(appId, name: "Internal Testers", isInternal: true)
5. beta_groups_add_builds(groupId, [buildId])
6. builds_send_beta_notification(buildId) → notify testers (optional)

Tip: Internal testers (up to 100) get builds immediately. External testers (up to 10,000) require Beta App Review for the first build of each version.


Workflow: Review Management

Monitor and respond to App Store reviews.

1. apps_search(query: "MyApp")           → get app ID
2. reviews_list(appId, sort: "-createdDate", limit: 20)
   OR reviews_list(appId, filterRating: "1,2")  → negative reviews only
3. reviews_stats(appId)                  → rating distribution summary
4. reviews_create_response(reviewId, responseBody: "Thank you for...")

Response guidelines:

  • Respond to negative reviews within 24-48 hours
  • Be professional and offer specific help
  • Updating a response replaces the previous one (users see "Developer Response")

Workflow: Feedback Triage

Correlate TestFlight feedback with build diagnostics.

1. builds_list(appId, limit: 10)         → recent builds
2. builds_get_beta_testers(buildId)      → who tested this build
3. metrics_build_diagnostics(buildId)    → crash signatures for this build
4. metrics_get_diagnostic_logs(signatureId) → individual crash logs

Limitation: TestFlight text feedback and screenshots are NOT available via the App Store Connect API. Use Xcode Organizer or the ASC web dashboard for feedback content.


Workflow: Multi-Company

Switch between App Store Connect teams.

1. company_list                          → see configured accounts
2. company_switch(companyId: "client-a") → switch active account
3. (All subsequent calls use client-a's credentials)

Multi-Company Setup

Add to ~/.config/asc-mcp/companies.json:

{
  "companies": [
    {
      "id": "my-company",
      "name": "My Company",
      "key_id": "KEY_ID_1",
      "issuer_id": "ISSUER_1",
      "key_path": "/Users/you/.keys/AuthKey1.p8"
    },
    {
      "id": "client-a",
      "name": "Client A",
      "key_id": "KEY_ID_2",
      "issuer_id": "ISSUER_2",
      "key_path": "/Users/you/.keys/AuthKey2.p8"
    }
  ]
}

Or use numbered environment variables: ASC_COMPANY_1_NAME, ASC_COMPANY_1_KEY_ID, etc.


Key Tool Quick Reference

Apps & Builds

ToolParametersReturns
apps_searchqueryApp ID, name, bundleId, platform
apps_listlimitAll apps in account
builds_listappId, limit, sortBuild number, version, processing state
builds_find_by_numberappId, buildNumberSpecific build details
builds_get_processing_statebuildIdPROCESSING, VALID, INVALID, etc.
builds_check_readinessbuildIdWhether build is ready for distribution

Versions & Submission

ToolParametersReturns
app_versions_createappId, platform, versionStringNew version in PREPARE_FOR_SUBMISSION
app_versions_attach_buildversionId, buildIdAttached build
app_versions_set_review_detailsversionId, contactEmail, notes, etc.Review details
app_versions_submit_for_reviewversionIdSubmitted for review
app_versions_cancel_reviewversionIdCancelled review
app_versions_releaseversionIdManual release
app_versions_create_phased_releaseversionId7-day phased rollout

TestFlight

ToolParametersReturns
beta_groups_createappId, name, isInternalNew group
beta_groups_add_testersgroupId, testerIdsUpdated group
beta_groups_add_buildsgroupId, buildIdsBuild distributed
builds_set_beta_localizationbuildId, locale, whatsNew"What to Test" text
builds_send_beta_notificationbuildIdTesters notified

Reviews & Metrics

ToolParametersReturns
reviews_listappId, sort, filterRating, limitReview entries
reviews_statsappIdRating distribution
reviews_create_responsereviewId, responseBodyDeveloper response
metrics_app_perfappIdApp-level performance metrics
metrics_build_diagnosticsbuildIdCrash signatures per build

API Constraints

ConstraintDetails
No emoji in metadataVersion "What's New", descriptions, keywords — use words, not emoji
Version stateOnly PREPARE_FOR_SUBMISSION versions are editable. Once submitted, create a new version to make changes.
JWT lifetime20-minute tokens, auto-refreshed by asc-mcp
Rate limitsApple enforces per-account limits. asc-mcp retries with exponential backoff on 429s.
Locale formatStandard codes: en-US, ja, de-DE, zh-Hans, ru
Build processingNewly uploaded builds take 15-30 minutes to process. Poll builds_get_processing_state before attaching.
Phased releaseOnly available after approval. Can pause/resume with app_versions_update_phased_release.

Gotchas

GotchaDetails
Build not foundBuild may still be processing. Check builds_get_processing_state — must be VALID.
"Version already exists"Can't create duplicate version strings. Use app_versions_list to check first.
Attach failsBuild must be processed AND the version must be in PREPARE_FOR_SUBMISSION.
Review details rejectedContact info fields have format requirements. Email must be valid, phone must include country code.
Wrong appapps_search is fuzzy. Verify the returned bundleId matches your target app.
Multi-company confusionAlways call company_current first to confirm which account is active before making changes.
Beta App ReviewFirst external TestFlight build per version requires review. Subsequent builds to the same version are auto-approved.
Missing analyticsanalytics_* tools require vendor_number in company config. Without it, sales/financial reports fail silently.

Anti-Rationalization

ThoughtReality
"I'll just use the ASC web dashboard"MCP tools are faster for repetitive tasks — respond to 20 reviews, distribute to 5 groups, create versions across apps.
"I don't need worker filtering"208 tools consume ~30K tokens of context. Filter to what you need.
"I'll submit without review details"Submission will fail. app_versions_set_review_details is required before app_versions_submit_for_review.
"I'll skip company_current — I only have one account"Multi-company configs persist between sessions. Always verify.
"Feedback triage is the same via API"Text feedback and screenshots are NOT in the ASC API. Use Organizer for feedback content, MCP for crash diagnostics.

When asc-mcp is NOT Available

If asc-mcp is not configured, fall back to manual workflows:

  • Crash analysis: Use Xcode Organizer (see axiom-testflight-triage) or App Store Connect web dashboard (see axiom-app-store-connect-ref)
  • TestFlight distribution: Use Xcode → Product → Archive → Distribute, or xcodebuild + altool
  • Review management: Use App Store Connect web dashboard
  • Submission: Use Xcode → Product → Archive → Distribute to App Store

Resources

Skills: axiom-app-store-submission, axiom-app-store-ref, axiom-app-store-connect-ref, axiom-testflight-triage

Agents: crash-analyzer, security-privacy-scanner, iap-auditor

平台分布

Codex

36.69%
按下载量换算288

Claude

31.1%
按下载量换算244

Cursor

17.46%
按下载量换算137

Gemini CLI

10.02%
按下载量换算79

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills