Ateam MCP logo

Ateam MCP

by ariekogan

Builds, validates, deploys, and tests multi-agent solutions on the ADAS platform through MCP.

Install Ateam MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ariekogan-ateam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ateam-ai/mcp"
      ],
      "env": {
        "ADAS_TENANT": "YOUR_VALUE_HERE",
        "ADAS_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings β†’ Developer β†’ Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passedβ€” started and listed 59 tools correctly (1mo ago).

Overview

ariekogan/ateam-mcp MCP server exposes ADAS platform operations to MCP-compatible AI clients over stdio or HTTP. It guides agents through specification lookup, solution and skill design, validation, deployment, testing, connector management, and solution inspection. Reach for ariekogan/ateam-mcp MCP server when you want an AI assistant to manage an ADAS multi-agent system instead of editing platform definitions manually.

Use cases

  • Build multi-agent customer support solutions on ADAS
  • Validate skills and solution definitions before deployment
  • Deploy changes from a GitHub-backed development workflow
  • Test skill, voice, notification, and connector behavior
  • Inspect solution health and asynchronous execution chains

Key features

  • ADAS specification and example discovery
  • Skill and solution design assistance
  • Validation and deployment workflows
  • Incremental definition patching
  • Multi-mode testing and chain inspection
  • Connector and UI plugin scaffolding

Tools59

What Ateam MCP lets your agent do. Expand a tool for its parameters.

Verified live~19.4k tokens of context

Security & health

What it can reach and how reliably it runs β€” from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev Β· @ateam-ai/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks β€” not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.5kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed59Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Ateam MCP works

What ariekogan/ateam-mcp MCP server does

ariekogan/ateam-mcp MCP server connects an MCP client to the ADAS platform for building and operating multi-agent solutions. It exposes tools for learning the platform specification, reviewing examples and workflows, designing skills, editing solution definitions, deploying changes, and checking runtime state.

The server supports both development and operational tasks. An agent can create or modify skills, add connectors and plugins, validate definitions before deployment, run skill or voice tests, inspect asynchronous execution chains, and list or inspect deployed solutions. Destructive operations such as deleting a solution, skill, or connector require explicit confirmation.

How it works

The MCP process communicates with an AI environment through stdio or HTTP, then sends authenticated HTTPS requests to the ADAS external API and Core runtime. The onboarding sequence starts with ateam_bootstrap, which returns platform guidance and example solution patterns. ateam_get_spec, ateam_get_examples, and ateam_get_workflows provide the reference material needed to author compatible definitions.

Tenant-aware operations require an explicit ateam_auth call. An API key can be obtained from the A-Team API-key page. Environment configuration alone does not replace this tool call. Global specification, example, and validation operations can work without tenant authentication.

Deployment targets the main branch when using ateam_build_and_run. A typical GitHub-backed workflow edits dev, reviews the diff, promotes changes to main, and then deploys. For smaller changes, ateam_patch can update selected fields and redeploy them. Its default array behavior merges protected arrays rather than silently replacing them, and dry_run:true can preview changes.

Setup and configuration

Install the published package with:

Terminal
npx -y @ateam-ai/mcp

For local development, the repository instructions use git clone, npm install, and npm start. The MCP client configuration examples provide two environment variables:

  • ADAS_TENANT: ADAS tenant identifier.
  • ADAS_API_KEY: API key used for tenant access.

The server can be configured in Claude Desktop, Claude Code, Cursor, Windsurf, or another MCP-compatible environment. The material also describes a hosted HTTP endpoint at https://mcp.ateam-ai.com.

Tools and capabilities

The provided tool set covers:

  • Bootstrapping, authentication, specification lookup, semantic specification search, examples, workflows, and design advice.
  • Creating, patching, inspecting, listing, and deleting solutions, skills, and connectors.
  • Deploying the main branch, uploading connector code, scaffolding connectors and UI plugins, and inspecting widget catalogs.
  • Testing skills, pipelines, voice flows, notifications, conversations, connectors, and asynchronous jobs.
  • Polling chain status, retrieving execution trees, and aborting running skill tests.

ariekogan/ateam-mcp MCP server is suited to conversational solution authoring, iterative deployment, integration testing, and runtime inspection. It is less suitable if you only need a generic MCP registry, a standalone model runtime, or a local tool unrelated to ADAS.

Limitations and notes

Deployment and tenant-specific inspection require authentication and access to the ADAS platform. ateam_conversation is asynchronous and returns a chain identifier; callers should poll ateam_chain_status until the complete chain finishes rather than repeatedly fetching the full chain tree. ateam_build_and_run is a heavy operation that can take 60–180 seconds and always deploys main.

Deletion operations are irreversible within ADAS Core and require confirmation parameters. Connector deletion can break skills that reference its tools.

The project is released under the MIT license.

Reviews

No reviews yet β€” be the first to share how it worked for you.

Frequently Asked Questions about Ateam MCP

Run `npx -y @ateam-ai/mcp`, or clone the repository, run `npm install`, and start it with `npm start`.

Yes. The setup examples show Claude Desktop using `npx -y @ateam-ai/mcp` with `ADAS_TENANT` and `ADAS_API_KEY` environment variables.

Tenant-aware operations require an ADAS API key and an explicit `ateam_auth` call. The documented variables are `ADAS_TENANT` and `ADAS_API_KEY`.

Yes. `ateam_build_and_run` deploys the current `main` branch to A-Team Core, while other tools support patching, connector uploads, and testing.

Related MCP servers

Add a badge to your READMEShow it’s listed β€” live SVG, Markdown or HTML.

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 PreviewAteam MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ariekogan-ateam-mcp?style=directory)](https://allmcps.com/mcp/ariekogan-ateam-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ariekogan-ateam-mcp"><img src="https://allmcps.com/api/badge/ariekogan-ateam-mcp?style=directory" alt="Ateam MCP on AllMCPs" /></a>