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 分

    請在儲存庫或註冊中心條目中宣告授權條款。