MCP server for [Appcircle](https://appcircle.io): exposes Build, Signing Identities, Testing Distribution, Enterprise App Store, Publish to Stores
Appcircle MCP MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. 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.
Once Appcircle MCP is connected, these are the calls the assistant has available:
CLI — ** --exclude toolset1 toolset2 or --exclude-toolsets toolset1,toolset2Env — ** APPCIRCLE_EXCLUDED_TOOLSETS=build_module,reportget_build_profiles — Get build profiles for the current organization (paginated). Optionally filter by profile namepage — 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 by name (case-insensitive partial match). (string, optional)get_build_profile_details — Get a single build profile by ID, optionally including its build configurationsprofile_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 IDconfiguration_id — The build configuration ID (e.g. UUID). (string, required)get_build_profile_workflows — Get workflows for a build profile by profile IDBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 6 environment variables: APPCIRCLE_ACCESS_TOKEN, APPCIRCLE_API_URL, APPCIRCLE_MCP_ALLOWED_HOST, APPCIRCLE_TEST_ORGANIZATION_ID, APPCIRCLE_TEST_BRANCH_ID, APPCIRCLE_TEST_COMMIT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Appcircle MCP's toolset — CLI, Env, get_build_profiles and 11 more — is a fair guide to whether it matches your workflow. It is maintained by appcircleio; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| CLI | ** --exclude toolset1 toolset2 or --exclude-toolsets toolset1,toolset2 |
| Env | ** APPCIRCLE_EXCLUDED_TOOLSETS=build_module,report |
| get_build_profiles | Get build profiles for the current organization (paginated). Optionally filter by profile name. |
| 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 by name (case-insensitive partial match). (string, optional) |
| get_build_profile_details | Get a single build profile by ID, optionally including its build configurations. |
| 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. |
| configuration_id | The build configuration ID (e.g. UUID). (string, required) |
| get_build_profile_workflows | Get workflows for a build profile by profile ID. |
| get_workflow_detail | Get a single workflow by build profile ID and workflow ID. |
| workflow_id | The workflow ID (e.g. UUID). (string, required) |
{
"mcpServers": {
"appcircle": {
"command": "appcircle-mcp",
"args": ["--exclude", "report"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| APPCIRCLE_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| APPCIRCLE_API_URL | Endpoint or connection string the server talks to. | Yes |
| APPCIRCLE_MCP_ALLOWED_HOST | Endpoint or connection string the server talks to. | Optional |
| APPCIRCLE_TEST_ORGANIZATION_ID | Configuration value read at startup. | Optional |
| APPCIRCLE_TEST_BRANCH_ID | Configuration value read at startup. | Optional |
| APPCIRCLE_TEST_COMMIT_ID | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.