AAM-aware agents will detect manifests natively. Until then, a small MCP server we ship at examples/mcp-bridge lets any MCP-aware agent (Claude Desktop, Continue, Cody, plus generic stdio runners) discover and invoke AAM actions. One bridge, every AAM site.
The bridge is intentionally bootstrap scaffolding — its end state is obsolescence when AI labs add /.well-known/agent-actions.json detection to their existing browser tools. See the spec for the long-term plan.
Claude Desktop reads MCP server configs from a JSON file. Add the bridge as one entry; it shows up in the tool palette as 'aam_*' tools (e.g. aam_discover, aam_invoke).
01Build the bridge from the repo
Until the npm package lands, clone and build locally. The bridge has zero dependencies on whatcanido infrastructure — it speaks straight to AAM manifests.
bash
# Install (until @aam/mcp-bridge lands on npm)
git clone https://github.com/Tedysek01/aam-sdk.git
cd aam-sdk/examples/mcp-bridge
npm install
npm run build
# Note the absolute path — you'll point your agent at it next:
echo "$(pwd)/dist/index.js"
02Edit Claude Desktop's configmacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Add the bridge as an MCP server. Use the absolute path you printed above.
Quit (Cmd+Q on macOS, not just close window) and relaunch. You should see 'aam-bridge' in the tool list — try a prompt like 'list AAM tenants on whatcanido.dev' or point it at any AAM-enabled site.
04(Once published) the npm path
We'll keep this section updated. After @aam/mcp-bridge ships to npm:
bash
# Once we publish (queued — see /roadmap):
npm install -g @aam/mcp-bridge
# Then in your agent config, point at the global bin:
# command: aam-mcp-bridge