Getting started / Quickstart
Getting started
Connect any MCP-capable client to tam and drive your workspace programmatically — create issues, move sprints, search and read docs — all over the Model Context Protocol. No UI required, and every call is audited.
1 · Connect
Authorize a scoped service account for your workspace with a single command. tam exposes a hosted MCP endpoint over OAuth 2.1 — the CLI opens your browser, you approve the scope, and the credentials are stored locally for your client.
2 · Your first call
Every object in tam — issues, tasks, docs and sprints — is reachable as a typed tool call. Create a story and tam returns its key; from the same session an agent can update status, comment, link work, or fetch a doc.
3 · Assign work to an AI
Service accounts are first-class principals. Assign an issue to one exactly as you would a teammate, and an executor — Claude Code, Codex, or any MCP client — claims it, does the work, and writes its progress back to tam.
Each service account carries only the scopes you grant, and every read and write lands in the workspace audit log — so you always know which AI changed what, and when.