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:
- Sign in — in your browser.
- Confirm — which agents, and where.
- 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.
Metadata
Release files for ama-cli 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ama_cli-0.1.0.tar.gz | 59.4 kB | With provenance | Details for ama_cli-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ama_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ama_cli-0.1.0-py3-none-any.whl |
Total release size: 100.1 kB
Release files / ama_cli-0.1.0.tar.gz
| Download URL | ama_cli-0.1.0.tar.gz |
|---|---|
| Size | 59.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5ac462343137fb4e1d372e70936a52497df8f2d99b90b445c06e43aca614665
|
|
BLAKE2b-256 checksum How to use checksums |
cc79092ccac7131c4dbcbff8a4852218a1f818f8eb3785d3fd676dd94a0e6793
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2026.
Transparency logRelease files / ama_cli-0.1.0-py3-none-any.whl
| Download URL | ama_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 40.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c51ed6b7f34d953d4ff588d873829e90bddc71fc9a15fae949d5f35af16d93a4
|
|
BLAKE2b-256 checksum How to use checksums |
23f5ae5b2cb68de7ed60836ee228c56ccade3b903009ebf1990cc29a98f92193
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2026.
Transparency logSecurity for ama-cli 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ama_cli-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.