Skip to content
AADM
MCP

▸ 10 clients · one Streamable HTTP endpoint · no per-team forks

Any MCP-capable IDE. Same standard.
Same wire.

The wire

One endpoint, one transport, one config. Cursor, Claude Code, Windsurf, Cline, JetBrains AI, Zed, claude.ai Connectors, even raw curl — they all paste the same MCP server URL.

AADM is delivered over Streamable HTTP MCP. Anything that can speak the protocol gets the same workflows, gates, doctrine, and tools — so your team's discipline is no longer per-engineer or per-editor.

The harness is the part of the stack that decides what your agent can actually run. Agentic engineering covers why swapping harnesses should change nothing about how the work is governed.

The universal snippet Get access

One snippet, every IDE.

This is the canonical config. Most MCP-capable clients take this verbatim under their mcpServers key. Edit the Authorization header with your token.

mcpServers.aadm 
{
  "mcpServers": {
    "aadm": {
      "type": "http",
      "url": "https://mcp.aadm.io/mcp",
      "headers": {
        "Authorization": "Bearer <your token here>"
      }
    }
  }
}

Three universal rules

  • 01 The URL must include /mcp.
  • 02 type: http means Streamable HTTP, not stdio.
  • 03 Use Bearer ak_… for API keys, or just aadm_… for dashboard tokens.

Some clients (claude.ai, Claude Code) prefer OAuth instead — see OAuth setup.

AI-native editors.

Native chat + tool calls. Pasting the MCP snippet wires AADM directly into the agent.

  • A

    CLI · IDE-adjacent

    Claude Code (terminal)

    Runs against your working tree — read, search, diff, test, multi-step refactors. Ideal for Investigator loops where MCP supplies gates and the CLI supplies evidence.

    Best for

    Long debugging sessions, code-first agent work

    Bearer · OAuth ~/.claude.json
    Setup guide
  • B

    GUI

    Claude Desktop

    Best for docs-centric sessions, walking stakeholders through standard_brief outputs, and paste-style debugging from logs and HAR excerpts.

    Best for

    Planning, stakeholder review, doctrine reading

    Bearer · OAuth claude_desktop_config.json
    Setup guide
  • C

    AI-native editor

    Cursor

    Standard as coaching, Cursor as editor. AADM loads workflows and gates over MCP; Cursor opens your project and applies them to real code.

    Best for

    Day-to-day feature work and refactoring

    Bearer · ak_ ~/.cursor/mcp.json
    Setup guide
  • D

    AI-native editor

    Windsurf

    Wires the same Streamable HTTP MCP — paste the universal snippet into the IDE's MCP settings. Check Windsurf's MCP docs for any current overrides.

    Best for

    Cursor alternatives, multi-agent workflows

    Bearer · ak_
    Use universal snippet

VS Code extensions.

Bring AADM into VS Code via an extension's MCP servers panel — no editor switch required.

  • E

    Extension

    Cline (VS Code)

    Open-source agentic coding extension for VS Code. Adds AADM MCP via its MCP servers panel — paste the universal snippet and reload.

    Best for

    VS Code users who want agent loops without leaving the editor

    Bearer · ak_
    Use universal snippet
  • F

    Extension

    Continue (VS Code / JetBrains)

    Continue's MCP support is evolving — check the latest docs for whether Streamable HTTP servers are configured via mcpServers JSON or the GUI. Universal snippet is the starting point.

    Best for

    Teams already on Continue who want governed lanes

    Bearer · ak_
    Use universal snippet

General editors.

IDEs whose AI assistants support MCP servers. The universal snippet is the starting point.

  • G

    JetBrains IDEs

    JetBrains AI Assistant

    MCP support landed in recent JetBrains AI Assistant releases. Configure the AADM server via the Settings → AI Assistant → MCP panel using the universal snippet.

    Best for

    IntelliJ, PyCharm, GoLand, Rider, WebStorm users

    Bearer · ak_
    Use universal snippet
  • H

    Editor

    Zed

    Zed's assistant supports MCP servers. Add AADM via the Zed settings (context servers) using the same Streamable HTTP URL and Bearer header pattern.

    Best for

    Performance-focused editor users

    Bearer · ak_
    Use universal snippet

Web · headless · scripts.

claude.ai Connectors (web) and raw curl (CI, custom hosts). Both speak the same Streamable HTTP wire.

  • I

    Web · custom connector

    claude.ai · Connectors

    Settings → Connectors → Add custom connector. Server URL and OAuth required — paste your client ID from the AADM member area. Don't use an API key here.

    Best for

    claude.ai web users who want AADM tools in chat

    OAuth
    OAuth setup
  • J

    CI · scripts · anything

    curl · raw HTTP

    Streamable HTTP is just JSON-RPC over POST. Anything that can send an Authorization header and accept SSE can call the MCP — CI checks, custom orchestrators, your own glue.

    Best for

    Build pipelines, custom hosts, smoke tests

    Bearer · ak_
    Smoke test snippet

Same three steps, every time.

  1. 01

    Get a token or client ID

    Bearer ak_… from Member area → API keys. Or OAuth Client ID from Member area → MCP OAuth.

    Member area

  2. 02

    Paste the snippet

    Drop the universal mcpServers.aadm block into the IDE's MCP settings file or panel.

    Universal snippet

  3. 03

    Reload

    Restart the IDE (or restart the MCP) so tools/list picks up the AADM server. Ask the agent for standard_brief to confirm.

    Tools catalog

Pick an IDE. Paste a snippet.
Ship governed.

The standard is free. The hosted MCP is a subscription. The IDE you already use is the one that connects.

Connect production agents Read the standard Browse the tools catalog
Clients listed · 10
Transport · Streamable HTTP / MCP
Endpoint · https://mcp.aadm.io/mcp