# Axon

> Axon (axonjira.com) is a free, Jira-like project manager: sprints, Kanban boards, backlog, epics, versions, native timesheets, a ticket desk, Slack and GitHub integrations, and outgoing webhooks. Agents can drive a project through the v1 REST API, the `axon` CLI, or the `axon-mcp` MCP server, all published on npm as `axonjira`.

- Free to use; no paid tier is required for the API, CLI or MCP server.
- Setup: any project member creates their own API key in the app under Settings -> API Keys, then runs `bunx axonjira login` (or `bun add -g axonjira` and `axon login`) and pastes it; `axon task list` works from then on. Over HTTP, send it as `Authorization: Bearer axj_<keyId>.<secret>`. Header only - a key in the query string is refused.
- A key acts as the person who created it and can do only what their project role allows in the app: viewer - read; member - read, move tasks, comment, edit their own tasks, raise tickets; admin or owner - everything. It stops working if they leave the project or the project is deleted, and its scopes drop if their role is lowered.
- One key = one project. Every REST path except `GET /api/v1/me` carries that project's `{projectId}`; call `/me` (or the `axon_whoami` tool) first to learn the project id and its workflow status ids. The CLI and MCP server do this for you, so they need only the key.
- Scopes are ranked, not additive: `read < write < admin`, capped by the creator's role. GET needs read, POST/PATCH need write, every DELETE (and starting/completing a sprint) needs admin.

MCP client config (e.g. `.mcp.json`):

```json
{
  "mcpServers": {
    "axon": {
      "command": "bunx",
      "args": [
        "--package",
        "axonjira",
        "axon-mcp"
      ],
      "env": {
        "AXON_API_KEY": "axj_<keyId>.<secret>"
      }
    }
  }
}
```

## Docs

- [CLI & MCP reference](https://www.axonjira.com/api/cli): every `axon` command and `axon-mcp` tool, generated from the CLI's own declarations
- [REST API docs](https://www.axonjira.com/api/v1/docs): interactive reference for the v1 REST API
- [OpenAPI spec](https://www.axonjira.com/api/v1/openapi.json): OpenAPI 3.1 document for the v1 REST API
- [llms-full.txt](https://www.axonjira.com/llms-full.txt): this file plus the full CLI, MCP tool and REST endpoint reference in one document

## Tools

- [npm package](https://www.npmjs.com/package/axonjira): `axonjira` - the `axon` CLI and the `axon-mcp` MCP server
- [MCP quick config](https://www.axonjira.com/api/cli#mcp): run `bunx --package axonjira axon-mcp` with `AXON_API_KEY` set, or after `axon login`

## Optional

- [Landing page](https://www.axonjira.com/en): product overview
- [Privacy policy](https://www.axonjira.com/en/privacy)
- [Terms of service](https://www.axonjira.com/en/terms)