Appcircle MCP

MCP server for Appcircle mobile CI/CD platform.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Remote HTTP

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "appcircle-mcp": {
      "url": "https://api.appcircle.io"
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (80)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Appcircle MCP.

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.

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)

Documentation Overview

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 <token>`) 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 - Installation guide for Claude Desktop and Claude Code CLI.
Cursor IDE - Installation guide for Cursor IDE.
Codex - Installation guide for Codex app and Codex CLI.
Antigravity IDE - Installation guide for Antigravity IDE.
VS Code (GitHub Copilot) - Installation guide for VS Code with GitHub Copilot.
Windsurf IDE - Installation guide for Windsurf IDE.
Gemini CLI - Installation guide for Gemini CLI.
GitHub Copilot CLI - 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:

config.json

{
  "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)

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit

4d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Appcircle MCP

Appcircle MCP is a hosted MCP server. Add it as a remote server in your client's config: "mcpServers": { "appcircle-mcp": { "url": "https://api.appcircle.io" } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/appcircle-mcp?style=directory)](https://allmcps.com/mcp/appcircle-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/appcircle-mcp"><img src="https://allmcps.com/api/badge/appcircle-mcp?style=directory" alt="Appcircle MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

11/16 checks healthy over the last 46d

49Quality signal: Fair · 49/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools23/30

Adoption & activity4/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Appcircle MCP →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients