Ateam Mcp

io.github.ariekogan由 GitHub 账号 ariekogan 发布v0.1.2更新于 Oct 24, 2026

Build, validate, and deploy multi-agent AI solutions from any AI environment.

已验证Streamable HTTP可网页运行云端与基础设施开发者工具AI 与机器学习

概览

AI 生成的概览

把 AI 助手接入 ADAS 平台,使其能读取规范、构建、校验并部署多智能体解决方案与技能。

可以做什么
  • 读取 ADAS 规范,以及技能、连接器和解决方案的完整可用示例
  • 校验技能定义与整体解决方案,包括跨技能契约与质量评分
  • 部署解决方案、向已有方案添加技能、部署连接器,并把改动重新上线
  • 列出并查看已部署方案的定义、技能、健康状态、状态与导出
  • 增量更新方案或技能,并与 Solution Bot 对话获取改造建议
  • 打开私有工作区、在其中执行命令、查看状态、保存成果并关闭
适用场景
适合希望让助手在 ADAS 平台上编写并上线多智能体系统、而不必手写 JSON 或在文档、编辑器与仪表盘之间来回切换的场景。也适合需要反复校验、部署并检查技能与方案健康状态的迭代工作。
运行要求
需要远程 Streamable HTTP 端点,或通过 npx 运行本地 npm 包;每次请求都要带 OAuth 登录或作为 Authorization Bearer 头发送的 A-Team 工作区 API 密钥。密钥需由工作区所有者或管理员提供,本地进程只能通过其登录工具完成登录。需要能访问 ADAS API 的网络。
安装前请注意
部署、重新部署、更新和保存工作区等操作会改动线上生产系统。工作区密钥可访问整个工作区,应避免粘贴到对话中,而通过登录流程或客户端配置传入。工作区执行工具会在托管工作区中运行任意命令,请求也会转发给 ADAS 平台与 API。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Ateam Mcp,将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.ariekogan%2Fateam-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "ateam": {
      "type": "http",
      "url": "https://mcp.ateam-ai.com/mcp"
    }
  }
}

README

ateam-mcp

Give any AI the ability to build, validate, and deploy production multi-agent systems.

This is an MCP server that connects AI assistants — ChatGPT, Claude, Gemini, Copilot, Cursor, Windsurf, and any MCP-compatible environment — directly to the ADAS platform.

An AI developer says "Build me a customer support system with order tracking and escalation" — and their AI assistant handles the entire lifecycle: reads the spec, builds skill definitions, validates them, deploys to production, and verifies health. No manual JSON authoring, no docs reading, no copy-paste workflows.

Why this matters

Today, building multi-agent systems requires deep platform knowledge, manual configuration, and switching between docs, editors, and dashboards. ateam-mcp eliminates all of that by making the ADAS platform a native capability of the AI tools developers already use.

The AI assistant becomes the developer interface:

Developer: "Create an identity verification agent that checks documents,            validates faces, and escalates fraud cases"
AI Assistant:  → reads ADAS spec (adas_get_spec)  → studies working examples (adas_get_examples)  → builds skill + solution definitions  → validates iteratively (adas_validate_skill, adas_validate_solution)  → deploys to production (adas_deploy_solution)  → verifies everything is running (adas_get_solution → health)
Developer: "Add a new skill that handles address verification"
AI Assistant:  → deploys into the existing solution (adas_deploy_skill)  → redeploys (adas_redeploy)  → confirms health

No context switching. No manual steps. The full ADAS platform — specs, validation, deployment, monitoring — is available as natural language.

How it reaches the AI community

ChatGPT users

ChatGPT supports MCP connectors in Developer Mode. Users connect by pasting a single URL:

Settings → Connectors → Developer Mode → paste https://mcp.ateam-ai.com

That's it. All 12 ADAS tools appear in ChatGPT. Any ChatGPT Pro, Plus, Business, or Enterprise user can build and deploy multi-agent solutions through conversation.

Claude users

claude.ai and Claude Desktop — add the hosted connector: open Customize > Connectors (Claude Desktop: Customize in the sidebar, then Connectors), click Add custom connector, enter https://mcp.ateam-ai.com, and click Connect. The A-Team sign-in page opens in the browser and asks for your workspace's key: copy it from app.ateam-ai.com/connect (a workspace owner or admin) and paste it there. The key decides the workspace; to switch, Disconnect and Connect again with the other workspace's key.

Claude Code — the hosted connector, signed in the same way:

bash
claude mcp add --transport http ateam https://mcp.ateam-ai.com

then /mcp and authenticate in the browser.

Never paste a key into a chat. ateam_bootstrap's session field says which workspace a session is on and how to switch.

Cursor / Windsurf / VS Code (Copilot)

Add the hosted server to .cursor/mcp.json, mcp_config.json, or .vscode/mcp.json:

json
{  "mcpServers": {    "ateam": { "url": "https://mcp.ateam-ai.com/mcp" }  }}

A client with OAuth opens the A-Team sign-in page; one without sends the key as Authorization: Bearer <key> from its own config (see below). A local process (npx -y @ateam-ai/mcp) signs in only through ateam_auth: an ADAS_API_KEY in its environment does not sign it in.

Gemini and other platforms

As MCP adoption grows (it's now governed by the Agentic AI Foundation under the Linux Foundation, co-founded by Anthropic, OpenAI, and Block), every AI platform that implements MCP gets access to ateam-mcp automatically. The remote HTTP endpoint (https://mcp.ateam-ai.com, also at /mcp) works with any client that supports Streamable HTTP transport.

The HTTP endpoint needs a credential on every request: OAuth (clients that support it follow the 401 challenge on their own), or your A-Team API key sent as Authorization: Bearer <key>. An anonymous request is refused with 401; since 0.4.93 there is no anonymous session to call ateam_auth from. See CHANGELOG.md.

Discovery

Developers find ateam-mcp through:

  • npm — npm search mcp ai-agents → @ateam-ai/mcp
  • Official MCP Registry — registry.modelcontextprotocol.io
  • Claude Desktop Extensions — built-in extension browser
  • Claude Code Plugin Marketplace — /plugin → Discover tab
  • Windsurf MCP Marketplace — built-in marketplace
  • VS Code MCP Gallery — Extensions view
  • Community directories — Smithery, mcp.so, PulseMCP (30,000+ combined listings)

Available tools

ToolWhat it does
adas_get_specRead the ADAS specification — skill schema, solution architecture, enums, agent guides
adas_get_examplesGet complete working examples — skills, connectors, solutions
adas_validate_skillValidate a skill definition through the 5-stage pipeline
adas_validate_solutionValidate a solution — cross-skill contracts + quality scoring
adas_deploy_solutionDeploy a complete solution to production
adas_deploy_skillAdd a skill to an existing solution
adas_deploy_connectorDeploy a connector to ADAS Core
adas_list_solutionsList all deployed solutions
adas_get_solutionInspect a solution — definition, skills, health, status, export
adas_updateUpdate a solution or skill incrementally (PATCH)
adas_redeployPush changes live — regenerates MCP servers, deploys to ADAS Core
adas_solution_chatTalk to the Solution Bot for guided modifications
ateam_workspace_openFor a chat agent with no shell: open one private workspace (files in /workspace) for the conversation
ateam_workspace_execRun one command in the workspace (100 s foreground; run_in_background for long builds)
ateam_workspace_statusCheck the workspace: unsaved changes, a long save or background command
ateam_workspace_saveMake the workspace's work live (the only way the other tools see it)
ateam_workspace_closeFinish; optionally save first. Brings back the single-file write tools withheld while it was open

The ateam_workspace_* tools are listed whenever you are signed in. A workspace the platform cannot give (a trial workspace, a key tied to no person) is refused by the call itself, with the single-file tools to use instead.

Setup

bash
# Clonegit clone https://github.com/ariekogan/ateam-mcp.gitcd ateam-mcp
# Installnpm install
# Run (a local stdio process)npm start

A local process signs in with ateam_auth, given a workspace key the agent reads from a file outside the chat; an ADAS_API_KEY in the environment does not sign it in and is never sent. ADAS_API_URL in its environment points it at a self-hosted API. Most people use the hosted connector instead (above).

Architecture

┌─────────────────────────────────────────────┐│  AI Environment                             ││  (ChatGPT / Claude / Cursor / Windsurf)     ││                                             ││  Developer: "build me a support system"     │└──────────────────┬──────────────────────────┘                   │ MCP protocol                   │ (stdio or HTTP)┌──────────────────▼──────────────────────────┐│  ateam-mcp                                  ││  12 tools — spec, validate, deploy, manage  │└──────────────────┬──────────────────────────┘                   │ HTTPS                   │ X-ADAS-TENANT / X-API-KEY┌──────────────────▼──────────────────────────┐│  ADAS External Agent API                    ││  api.ateam-ai.com                           │└──────────────────┬──────────────────────────┘                   │┌──────────────────▼──────────────────────────┐│  ADAS Core                                  ││  Multi-agent runtime                        │└─────────────────────────────────────────────┘

License

MIT

来源:README.md,提交 03c419d

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.1.2最新Sep 16, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。