ama-cli 0.1.0

Connect your coding agent to Ama.

ama

Connect your coding agent to Ama.

curl -fsSL https://ama.dev/install | sh

That installs the CLI and runs ama onboard. Three questions and you are done:

1. Sign in — in your browser.
2. Confirm — which agents, and where.
3. Start now? — opens your agent on a live notebook.

Already have the CLI?

ama onboard

Re-running either line upgrades.

Commands

Command	Does
ama onboard	Sign in, detect agents, register MCP. Start here.
ama detect	Show which coding agents were found, and why.
ama login / logout / whoami	Manage credentials.
ama mcp add / list / remove	Manage MCP registration directly.

Supported agents

Registered automatically:

Agent
Claude Code	claude mcp add -s user
Cursor	~/.cursor/mcp.json
Codex CLI	codex mcp add — also export AMA_API_KEY; Codex stores the variable name, not the token
Gemini CLI	gemini mcp add
VS Code (Copilot)	code --add-mcp

Detected but not yet registered automatically: Windsurf, Zed, Cline, Roo Code. ama onboard tells you rather than pretending, and prints what to paste.

ama detect explains what it found and where, so you can check before anything is written. ama onboard --dry-run prints the exact diff for every file it would touch — and signs in to nothing, so no key is created.

Self-hosted

Point at your own deployment; the CLI reads /.well-known/mcp.json for the endpoint and auth method rather than assuming anything.

ama onboard --host https://ama.internal.example.com

Install without the script

uv tool install ama-cli    # binary is `ama`

Notes

This is the public client. It speaks HTTP to a hosted or self-hosted Ama and carries no server dependencies — typer and rich, nothing else.

Your API key is stored in ~/.ama/credentials.json, mode 0600. The CLI never writes a literal token into a project-scoped config file, since those get committed; project scope uses environment-variable indirection instead.

Licensed under Apache-2.0.