A-Team ADAS

{
  "id": "aix_4496f9ddac",
  "name": "A-Team ADAS",
  "operator": "(unclaimed - source: pulsemcp · publisher: github.com)",
  "description": "Connects AI assistants to the ADAS platform for building, validating, and deploying multi-agent solutions.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-29",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "browser-automation",
    "chat-messaging",
    "github-ops",
    "nosql-database"
  ],
  "protocols": {
    "mcp": "https://mcp.ateam-ai.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 606,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 66,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-29T01:00:35.227Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://www.pulsemcp.com/servers/ariekogan-ateam-adas"
    },
    {
      "label": "repository",
      "url": "https://github.com/ariekogan/ateam-mcp"
    },
    {
      "label": "listing",
      "url": "https://ateam-ai.com/"
    }
  ],
  "avatar": "https://github.com/ariekogan.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/ariekogan"
    }
  ],
  "public_stats": {
    "gh_stars": 1,
    "npm_downloads": 8780
  },
  "profile": {
    "mcp_server": "ateam-mcp",
    "mcp_version": "0.4.85",
    "tool_count": 57,
    "tools": [
      {
        "name": "ateam_bootstrap",
        "description": "REQUIRED onboarding entrypoint for A-Team MCP. MUST be called when user greets, says hi, asks what this is, asks for help, explores capabilities, or when MCP is first connected. Returns platform explanation, example solutions, and assistant behavior instructions. Do NOT improvise an introduction — call this tool instead."
      },
      {
        "name": "ateam_auth",
        "description": "Authenticate with A-Team. Required before any tenant-aware operation (reading solutions, deploying, testing, etc.). The user can get their API key at https://mcp.ateam-ai.com/get-api-key. Only global endpoints (spec, examples, validate) work without auth. IMPORTANT: Even if environment variables (ADAS_API_KEY) are configured, you MUST call ateam_auth explicitly — env vars alone are not sufficient. For cross-tenant admin operations, use master_key instead of api_key."
      },
      {
        "name": "ateam_get_spec",
        "description": "Get the A-Team specification — schemas, validation rules, system tools, agent guides, and templates. Start here after bootstrap to understand how to build skills and solutions. Use 'section' to get just one part of the skill spec (much smaller than the full spec). Use 'search' to find specific fields or concepts across the spec.\n\nWhen designing a persona that orchestrates logic via run_python_script (the Python-as-orchestrator pattern), also fetch topic='python_helpers' — that returns the adas.* helper namespace reference. Skills designed without knowing about adas.* produce 5-10x larger / bri"
      },
      {
        "name": "ateam_get_workflows",
        "description": "Get the builder workflows — step-by-step state machines for building skills and solutions. Use this to guide users through the entire build process conversationally. Returns phases, what to ask, what to build, exit criteria, and tips for each stage."
      },
      {
        "name": "ateam_get_examples",
        "description": "Get complete working examples that pass validation. Study these before building your own."
      },
      {
        "name": "ateam_design_advisor",
        "description": "CONSULT THIS DURING DESIGN — before and while you design a skill/solution. Describe what you're building; it returns POINTERS to the platform capabilities that fit (per-actor storage, widgets, triggers, sub-agents, mobile data, run-scripts, multi-skill, GitHub, …), each with the /spec topic to read next (via ateam_get_spec) and the tool to wire it. Also returns 'missing' hints (capabilities your goal implies but the design hasn't wired) and lifecycle hints (e.g. connect GitHub when the project will iterate). ADVISORY ONLY — you decide and own the design. Stateless: pass the current design_stat"
      },
      {
        "name": "ateam_spec_search",
        "description": "Semantic search over the FULL ateam platform /spec documentation — the deep fallback behind ateam_design_advisor. Ask a natural-language 'how do I…' question and get the most relevant doc chunks (with their topic + heading), then read the full topic via ateam_get_spec(topic). Use this when the advisor's pointer isn't enough, or for details/examples on anything — including topics outside the curated capability list. Read-only."
      },
      {
        "name": "ateam_build_and_run",
        "description": "DEPLOY THE CURRENT MAIN BRANCH TO A-TEAM CORE. ⚠️ HEAVIEST OPERATION (60-180s): validates solution+skills → deploys all connectors+skills to Core (regenerates MCP servers) → health-checks → optionally runs a warm test → auto-pushes to GitHub.\n\n🌳 DEV/PROD WORKFLOW:\n  1. Edit files → ateam_github_patch (writes to `dev` branch by default)\n  2. (Optional) Preview what's about to ship → ateam_github_diff\n  3. Ship dev → main → ateam_github_promote (merges + auto-tags `prod-YYYY-MM-DD-NNN`)\n  4. Deploy main to Core → ateam_build_and_run\n\nThis tool ALWAYS deploys the `main` branch — there is no `ref"
      },
      {
        "name": "ateam_test_skill",
        "description": "Send a test message to a deployed skill and get the execution result.\n\nWait modes (wait_for):\n  • 'root' (default, back-compat) — wait until the message's root job completes, return single-job result. Fast, ignores any sub-skills the root delegated to via askAnySkill.\n  • 'chain' — wait until EVERY job in the chain (root + handoffs + askAnySkill subcalls, recursively) reaches a terminal state, then return the full chain tree. Use when testing multi-skill flows (orchestrator → workers, builders → sub-builders, etc.). The response.chain field carries chainJobs[] with parentJobId/relation/depth a"
      },
      {
        "name": "ateam_test_notification",
        "description": "Fire a REAL notification at an existing actor in a deployed solution — for end-to-end testing of the system-initiated notification path (telegram/push/app channels).\n\nUnlike ateam_test_skill (synthetic test actor with no channels) and ateam_conversation (user-initiated thread), this calls the /api/internal/notify-user path that PCM and other sibling services use — so the actor's real enabled channels actually receive the message.\n\nUse for:\n  • Channel fan-out smoke (does telegram/push/app actually receive it?)\n  • Delivery-result verification (per-channel ok/failed in the response).\n\nAuth: for"
      },
      {
        "name": "ateam_conversation",
        "description": "Send a chat message to a deployed solution. No skill_id needed — the system auto-routes to the right skill.\n\nALWAYS ASYNC: returns a chain_id immediately — the assistant's reply is NOT in this response (a conversation can run for minutes across handoffs + subcalls, so a synchronous wait would hit the 100s edge timeout → 524).\n\nPOLL BY CHAIN, NEVER BY JOB: an individual job can terminate while the chain is still running, so poll ateam_chain_status(chain_id) on a loop (~2s) and stop when chain_done === true (or pending_question is set — the assistant is waiting on the user). That is the cheap ch"
      },
      {
        "name": "ateam_test_pipeline",
        "description": "Test the decision pipeline (intent detection → planning) for a skill WITHOUT executing tools. Returns intent classification, first planned action, and timing. Use this to debug why a skill classifies intent incorrectly or plans the wrong action."
      },
      {
        "name": "ateam_test_voice",
        "description": "Simulate a voice conversation with a deployed solution. Runs the full voice pipeline (session → caller verification → prompt → skill dispatch → response) using text instead of audio. Returns each turn with bot response, verification status, tool calls, and entities. Use this to test voice-enabled solutions end-to-end without making a phone call."
      },
      {
        "name": "ateam_patch",
        "description": "Surgically update ANY field in a skill or solution definition, redeploy, and optionally re-test — all in one step.\n\n⚠️ MERGE-BY-DEFAULT (v0.4.0) — Arrays are protected from silent replace. Bare array writes on solution.linked_skills / ui_plugins / platform_connectors / handoffs / grants / triggers (etc.) and skill.tools / connectors / handoffs / scenarios are REFUSED to prevent sibling loss. Add or remove items with the _push / _delete / _update suffixes; opt into a full-array replace only when you really mean it.\n\nOPERATIONS (safe by construction):\n1. Scalar (dot notation): { \"problem.stateme"
      },
      {
        "name": "ateam_get_solution",
        "description": "Read solution state — definition, skills, health, status, or export. Use this to inspect deployed solutions."
      },
      {
        "name": "ateam_list_solutions",
        "description": "List all solutions deployed in the Skill Builder."
      },
      {
        "name": "ateam_delete_solution",
        "description": "⚠️ IRREVERSIBLE — kills Mongo state, running MCP processes, and Builder FS for the whole solution and every skill. REQUIRES `confirm:true` AND `confirm_solution_id` echoing the solution id you're destroying (defeats typos and hallucinated ids). RECOVERY: the GitHub repo is untouched; `ateam_github_pull` rebuilds the solution from `main`. Prefer that over re-deploying from memory."
      },
      {
        "name": "ateam_delete_skill",
        "description": "⚠️ IRREVERSIBLE in Core + Builder FS — kills the running MCP process, unregisters from skill registry, deletes the Mongo record, drops from solution.skills[] and solution.linked_skills, and removes the skill's files from Builder FS. REQUIRES `confirm:true`. RECOVERY: the skill still lives in GitHub — `ateam_github_pull` rebuilds the whole solution (no per-skill restore path)."
      },
      {
        "name": "ateam_delete_connector",
        "description": "⚠️ CASCADING — any skill whose engine.bootstrap_tools or tools[] name a tool from this connector will FAIL its next execution. Stops and deletes the connector from A-Team Core; drops references from the solution definition (grants, platform_connectors, ui_plugins ids starting `mcp:<connector-id>:*`) and skill definitions (connectors array); cleans up mcp-store files. ALSO REMOVES THE SOURCE: `connectors/<id>/` is deleted from the repo (main AND dev) in the same call, so the delete is DURABLE. This CHANGED on 2026-08-23 — it used to preserve the source and name `ateam_build_and_run(github:true)"
      },
      {
        "name": "ateam_show_skill_minimal",
        "description": "Show the minimal authoring view of a skill — persona + connectors + handoff_when + style + policy guardrails only. ~10× smaller than ateam_get_solution(view:'skills') for the same skill. Use this when you only need the irreducible author content (Phase 9 of the strip)."
      },
      {
        "name": "ateam_show_solution_minimal",
        "description": "Show the minimal authoring view of a solution — name + description + style + routing_mode + identity_mode + skill ids + connector ids only. Skips deployed metadata, handoffs (auto-generated), grants, ui_plugins, validation results. Use this for fast inspection without the verbose fields (Phase 9 of the strip)."
      },
      {
        "name": "ateam_log_progress",
        "description": "Record that a build STEP is done, so a later run does not redo it. Write it AS IT HAPPENS, never at the end — the runs that most need a journal are the ones the clock kills.\n\nWHY: a continuation cannot otherwise tell what the previous run achieved, so it re-runs the whole orientation (bootstrap, get_workflows, list_solutions, get_solution, get_spec, get_examples, github_read) to re-derive from documents what was already established — and re-inflates its prompt into the region where provider latency collapses. Measured across 13 runs: stalls track PROMPT SIZE (~60k), not turn count. ateam_get_p"
      },
      {
        "name": "ateam_get_progress",
        "description": "What this build has already ACHIEVED — read it FIRST when continuing a run, before any orientation call. Returns the CURRENT status per step (latest entry wins) plus recent history.\n\nThen build only the steps that are ABSENT or not yet `verified`.\n\nABSENT IS NOT \"NOTHING WAS DONE\" — the journal may predate a step, or a run may have died before writing. It is a fast path, not a new source of truth: check before rebuilding something expensive.\n\nComplements ateam_get_lessons, which records what BROKE. This records what WORKS."
      },
      {
        "name": "ateam_log_lesson",
        "description": "Record ONE lesson this run learned, so the NEXT run does not relearn it. A building agent starts every run empty — it does not know which tool misled the last run or the workaround that got past it. Log a lesson the moment a tool misleads you AND you find a way through.\n\nAPPEND-ONLY. You cannot edit or delete earlier lessons, and you do not supply the timestamp — the server stamps it, so it cannot be forged.\n\nPROVENANCE CAVEAT, stated because the earlier wording over-promised: `job_id` and `actor` are recorded ONLY when the caller supplies x-adas-job-id / x-adas-actor-id. An agent calling this"
      },
      {
        "name": "ateam_get_lessons",
        "description": "Read what EARLIER runs on this solution learned — newest first, bounded. Call this during orientation, BEFORE planning: it is the only thing that carries context across runs, and it is cheap. Each entry says which tool misled a previous run, the verbatim error, what was tried instead, and whether that worked. An empty list is a real answer (nothing learned yet)."
      }
    ],
    "profiled_at": "2026-09-10T19:01:26.886Z"
  },
  "unreachable": false,
  "payment_method": "oauth"
}