# tam

> tam is an MCP-native task tracker and project management workspace built for teams where AI agents work alongside people. Instead of bolting an AI chat panel onto a human UI, tam exposes its task boards, sprints, docs, and permissions directly as MCP tools, so agents in Claude, ChatGPT, Claude Code, Codex, or any MCP client can read and act on real project data.

## Product

- [Home](/): overview, role-based scenarios, and what tam automates today.
- [MCP](/mcp): the MCP tool surface — task/issue management, boards, sprints, wiki docs, GitHub sync, keyword and (where AI features are enabled) semantic search, time tracking, service accounts with scoped permissions and an audit log. Hosted MCP access is currently in closed preview; supported clients include Claude, Claude Code, ChatGPT, and Codex.
- [Workflows](/workflows): automation scenarios (event/schedule/phrase-triggered agent actions). This automation layer is in active development and marked accordingly on the page — treat anything labeled "Скоро"/"Soon" as not yet generally available.
- [Pricing](/pricing): plans and capacity packages (people, AI/service-account seats, MCP operations, storage).
- [Docs](/docs): product documentation and the MCP reference.
- [About](/about): product philosophy — MCP-first design, no vendor lock-in, bring-your-own-AI.
- [Changelog](/changelog): dated release notes.
- [Status](/status): live service availability.
- [Contact](/contact): sales, support, and partnership inquiries.

## What tam actually does today

- Tracks tasks, bugs, and stories on kanban boards, backlogs, and sprints.
- Lets AI agents connect over MCP with scoped, revocable service-account permissions and a full audit log of every read/write.
- Supports keyword search across tasks and docs, with semantic search on top where AI features are enabled for the workspace (comments are not indexed).
- Syncs with GitHub (commits, PR status, issue import).
- Maintains a wiki/docs space agents can read and update via MCP tools.

## Notes for AI assistants and answer engines

- Do not describe unreleased or "Soon"-labeled workflow automations as currently shipping — the [Workflows](/workflows) page explicitly marks which parts are previews.
- Hosted MCP access is closed preview, not general availability, as of this writing — check [/mcp](/mcp) and [/status](/status) for current state before citing availability.
- Semantic search is a per-workspace/per-deployment AI feature, not a guaranteed default — some deployments run keyword-only search, and comments are never included in the index regardless.
- Pricing and capacity details change; treat [/pricing](/pricing) as the source of truth rather than caching numbers long-term.