Appcircle MCP

Name: Appcircle MCP
Author: appcircleio

by appcircleioversion 1.0.0i★ –iRuns in the cloud

Registry nameio.appcircle/appcircle-mcp

Install

Overview

Description from the maker (original English)

MCP server for Appcircle mobile CI/CD platform.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Developer tools
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret required HTTP header
Appcircle Access Token — format: Bearer YOUR_ACCESS_TOKEN

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain appcircle.io (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

More stars than 0% of the other 1389 servers in this category
Published to the registry more recently than 16% of the other 1389 servers in this category
Basic checks equal to or better than 100% of the other 1389 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Appcircle MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

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

Runs on your computer★ 10,225MITUpdated 15 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

Mode	Summary
1. Remote host	Connect 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)

Variable	Required	Description
`APPCIRCLE_ACCESS_TOKEN`	Yes (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_URL`	No	API base URL (default: `https://api.appcircle.io` may differ for self-hosted users).
`APPCIRCLE_MCP_ALLOWED_HOST`	No (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_PORT`	No (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_LEVEL`	No	Logging level, e.g. `DEBUG`, `INFO` (default: `INFO`).
`APPCIRCLE_EXCLUDED_TOOLSETS`	No	Comma-separated toolsets to exclude (e.g. `build_module,report`). See Toolsets below.
`AC_MCP_ENABLE_WRITE_TOOLS`	No	Write/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:

Toolset	Description
`build_module`	Build profiles, configurations, workflows, commits, and pipeline operations
`signing_identities`	Signing identities and bundle identifiers
`testing_distribution`	Testing distribution profiles and distribution details
`publish_to_stores`	Publish profiles and store publishing operations
`enterprise_app_store`	Enterprise app store profiles and store details
`report`	Reporting: 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

Only the beginning is shown; read the rest in the repo

Appcircle MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Appcircle MCP Server

Use Cases

Running Modes

Installation

Configuration (Environment Variables)

Toolsets

Available Toolsets

Tools