原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Appcircle MCP

作者:appcircleio版本 1.0.0i★ –i在云端运行
注册名称io.appcircle/appcircle-mcp

安装

概览

作者提供的说明(英文原文)

MCP server for Appcircle mobile CI/CD platform.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 开发者工具
  • 你需要填写:Authorization

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http appcircle https://mcp.appcircle.io --header 'Authorization: your-value'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "appcircle": {
      "url": "https://mcp.appcircle.io",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "appcircle": {
      "type": "http",
      "url": "https://mcp.appcircle.io",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • Authorization 机密 必填 HTTP header
    Appcircle Access Token — format: Bearer YOUR_ACCESS_TOKEN

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 appcircle.io 验证(注册中心会核实域名所有权)

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 1385 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1385 个服务器的 16% 更新
  • 基础检查结果等于或优于此分类中其他 1385 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Appcircle MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:Authorization

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.0.0)于6个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者:github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新
安装

Desktop Commander

作者:wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新
安装

Cloudflare MCP

作者:cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Appcircle MCP Server

MCP server for Appcircle: exposes Build, Signing Identities, Testing Distribution, Enterprise App Store, Publish to Stores, and Reporting tools to any MCP-capable client (Claude Desktop, Cursor, VS Code, etc.). The Appcircle MCP Server acts as the bridge between AI tools and Appcircle; thus, AI agents, assistants and chatbots to safely access and interact with Appcircle resources through structured, governed, and task-level tools.

Use Cases

  • CI/CD and Workflow Intelligence: Monitor pipeline runs, track release status, and get insights into your mobile CI/CD workflows.
  • Configuration and Environment Insights: Query build configurations and signing setup to understand how a project is configured and where issues may originate.
  • Reporting and Operational Insights: Generate summaries of CI stability, recurring issues, pipeline performance, and overall CI/CD health.

Running Modes

You can use the MCP server in four ways:

ModeSummary
1. Remote hostConnect to https://mcp.appcircle.io. No local install; your client sends your Appcircle token (e.g. Authorization: Bearer ) on each request.
2. Local (stdio)Run the server from source: clone the repo, optionally use a venv, then run appcircle-mcp (default transport is stdio). Requires Python and pip. Set APPCIRCLE_ACCESS_TOKEN in the environment. Your MCP client runs the server as a subprocess.
3. Local (streamable-http)Run the server locally over HTTP: use --transport streamable-http and optionally --host / --port (e.g. appcircle-mcp --transport streamable-http --host 127.0.0.1 --port 8000). Clients connect to that URL and send their token in the request.
4. Local (Docker)Run the official Docker image on your machine. Requires Docker. Use the image’s default port or override with --port; see the image documentation for exact usage.

Detailed client configuration (Cursor, Claude, etc.) lives in the dedicated installation guides; this section is a high-level summary only.

Installation

Client-specific setup guides:

  • [Claude Applications](docs/installation_guides/claude_applications.md) - Installation guide for Claude Desktop and Claude Code CLI.
  • [Cursor IDE](docs/installation_guides/cursor.md) - Installation guide for Cursor IDE.
  • [Codex](docs/installation_guides/codex.md) - Installation guide for Codex app and Codex CLI.
  • [Antigravity IDE](docs/installation_guides/antigravity.md) - Installation guide for Antigravity IDE.
  • [VS Code (GitHub Copilot)](docs/installation_guides/vscode.md) - Installation guide for VS Code with GitHub Copilot.
  • [Windsurf IDE](docs/installation_guides/windsurf.md) - Installation guide for Windsurf IDE.
  • [Gemini CLI](docs/installation_guides/gemini_cli.md) - Installation guide for Gemini CLI.
  • [GitHub Copilot CLI](docs/installation_guides/copilot_cli.md) - Installation guide for GitHub Copilot CLI.

Configuration (Environment Variables)

VariableRequiredDescription
APPCIRCLE_ACCESS_TOKENYes (stdio only)Appcircle API access token. Required when using stdio transport. For streamable-http, each client sends its own token. See Obtaining a token for how to get one.
APPCIRCLE_API_URLNoAPI base URL (default: https://api.appcircle.io may differ for self-hosted users).
APPCIRCLE_MCP_ALLOWED_HOSTNo (streamable-http only)Public hostname for the MCP server (e.g. mcp.appcircle.io). Set this when deploying behind a reverse proxy so the server accepts the Host header from clients. Omit for localhost.
APPCIRCLE_MCP_PORTNo (streamable-http only)Bind port for the HTTP server (default: 8000). Overridden by --port if provided. Useful for on-prem or Docker when a specific port is required.
LOG_LEVELNoLogging level, e.g. DEBUG, INFO (default: INFO).
APPCIRCLE_EXCLUDED_TOOLSETSNoComma-separated toolsets to exclude (e.g. build_module,report). See Toolsets below.
AC_MCP_ENABLE_WRITE_TOOLSNoWrite/action tools (e.g. trigger_build, cancel_build) are registered by default. Set to false/0/no/off to opt out and not register them at all (not just disable at call time).

Set these in your shell or in your MCP client’s configuration.

Toolsets

Available Toolsets

The following sets of tools are available:

ToolsetDescription
build_moduleBuild profiles, configurations, workflows, commits, and pipeline operations
signing_identitiesSigning identities and bundle identifiers
testing_distributionTesting distribution profiles and distribution details
publish_to_storesPublish profiles and store publishing operations
enterprise_app_storeEnterprise app store profiles and store details
reportReporting: build history, distribution, signing, publish status, and related reports

You can exclude one or more toolsets so their tools are not registered. Exclusions can be set via CLI arguments or the APPCIRCLE_EXCLUDED_TOOLSETS environment variable; both are merged (union).

  • CLI: --exclude toolset1 toolset2 or --exclude-toolsets toolset1,toolset2
  • Env: APPCIRCLE_EXCLUDED_TOOLSETS=build_module,report

Example MCP config (Cursor / Claude Desktop) with exclusions:

{

"mcpServers": { "appcircle": { "command": "appcircle-mcp", "args": ["--exclude", "report"] } } }

Tools

Tools are exposed via MCP tools/list. Reference below lists all tools by toolset; for response shape and examples see docs/tool_contract.md.

Build

  • get_build_profiles - Get build profiles for the current organization (paginated). Optionally filter by profile name, platform, last build status, and repository source. Optionally sort.
  • Access level: read
  • page: Page number (1-based). Default: 1. (number, optional)
  • size: Page size (1-100). Default: 25. Values above 100 are capped at 100. (number, optional)
  • search: Optional search term to filter profiles (case-insensitive partial match on profile name; the API's search may also match other profile fields). (string, optional)
  • platform: Optional list of platform codes to filter by. Allowed values: 1=iOS, 2=Android. (list of numbers, optional)
  • last_build_status: Optional list of last build status codes to filter by. Allowed values: 0=Success, 1=Failed, 2=Canceled, 3=Timeout, 90=Waiting, 91=Running. (list of numbers, optional)
  • repository_source: Optional list of repository source codes to filter by. Allowed values: 1=GitHub, 2=Bitbucket, 3=GitLab, 4=Azure DevOps, 6=Public Repository, 7=Private Repository, 8=SSH. (list of numbers, optional)
  • sort: Optional sort field code. Allowed values: 1=Profile Name, 2=Create Date, 3=Last Build Date. (number, optional)
  • sort_direction: Optional sort direction code. Allowed values: 1=ASC, 2=DESC. (number, optional)
  • get_build_profile_details - Get a single build profile by ID, optionally including its build configurations.
  • Access level: read
  • profile_id: The build profile ID (e.g. UUID). (string, required)
  • configurations: If true, also fetch the profile's build configurations. Default: false. (boolean, optional)
  • get_build_configuration_details - Get a single build configuration by profile ID and configuration ID.
  • Access level: read
  • profile_id: The build profile ID (e.g. UUID). (string, required)
  • configuration_id: The build configuration ID (e.g. UUID). (string, required)
  • get_build_profile_workflows - Get workflows for a build profile by profile ID.
  • Access level: read
  • profile_id: The build profile ID (e.g. UUID). (string, required)
  • get_workflow_detail - Get a single workflow by build profile ID and workflow ID.
  • Access level: read
  • profile_id: The build profile ID (e.g. UUID). (string, required)
  • workflow_id: The workflow ID (e.g. UUID). (string, required)
  • get_commits_by_branch - Get commits for a build branch (paginated).
  • Access level: read
  • branch_id: The branch ID (e.g. UUID). (string, required)
  • page: Page number (1-based). If provided with size, enables pagination. Default: 1. (number, optional)
  • size: Page size. If provided with page, enables pagination. Default: 25, max 100. (number, optional)
  • get_commit_details - Get a single commit by commit ID (UUID) or by commit hash (git SHA). Provide either commit_id or commit_hash, not both.
  • Access level: read
  • commit_id: The commit ID (UUID). (string, optional)
  • commit_hash: The commit hash (git SHA). (string, optional)
  • get_last_commit - Get the most recent commit on a build branch.
  • Access level: read
  • branch_id: The branch ID (e.g. UUID). (string, required)
  • get_build_status - Get the status of a build (e.g. 0=Success, 1=Failed, 2=Canceled, 3=Timeout, 90=Waiting, 91=Running, 92=Completing, 99=Unknown).
  • Access level: read
  • commit_id: The commit ID (UUID). (string, required)
  • build_id: The build ID (UUID). (string, required)
  • get_build_logs - Get the logs for a build, optionally scoped to a single step. Defaults to a tail-truncated view to avoid flooding the model's context.
  • Access level: read
  • commit_id: The commit ID (UUID). (string, required)
  • build_id: The build ID (UUID). (string, required)
  • step: Optional exact step name (case-insensitive) to scope output to one step's log block. (string, optional)
  • full_log: If true, return the entire log instead of the default tail. Still capped at 256 KB. Default: false. (boolean, optional)
  • tail_lines: Number of lines to keep from the end when not using full_log. Default: 200, max 1000. (number, optional)
  • grep: Case-insensitive substring filter applied to lines before truncation. (string, optional)
  • get_variable_groups - Get all build environment variable groups for the organization, including each group's variables (key, value, isSecret, isFile). Secret values are already redacted by the API.
  • Access level: read
  • Takes no parameters.
  • trigger_build - SIDE EFFECT: starts a new real build run (queues an actual build, consuming build minutes/credits) either on a branch (latest synced commit) or for one specific commit. Registered by default; set AC_MCP_ENABLE_WRITE_TOOLS=false to opt out.
  • Access level: write
  • profile_id: The build profile ID (e.g. UUID). Required in branch mode (commit_id not given); unused in commit mode. (string, optional)
  • workflow_id: The workflow ID (e.g. UUID). Required in branch mode. Optional in commit mode (uses the last-used/default workflow if omitted). (string, optional)
  • branch_name: Optional branch name (e.g. "main"). Branch mode only; falls back to the profile's default branch if omitted. Must not be given together with commit_id. (string, optional)
  • commit_id: The commit's own ID (not its git hash) to trigger a build for a specific commit instead of the latest one on a branch. Must not be given together with branch_name. (string, optional)
  • configuration_id: Optional build configuration ID (e.g. UUID) to use instead of the default. (string, optional)
  • cancel_build - SIDE EFFECT: cancels a queued or running build (real, in-progress work is stopped; cannot be resumed). Registered by default; set AC_MCP_ENABLE_WRITE_TOOLS=false to opt out.
  • Access level: write
  • task_id: The build's task ID (the "taskId" field returned by trigger_build). (string, required)

Signing Identities

  • **get_bund

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx