Give your AI the tools to do real work.
tam speaks MCP. Your AI assistant – Claude, for example – can read your workspace context, close tasks, and move the board right from its own interface, no switching to a tracker.
Analyzed 12 workspace tasks, found 2 blockers and raised their priority
How this changes your day
Work in the chat you already use
No need to open the tracker. Tell your AI: "File a bug on the login flow" – the task shows up on the tam board instantly.
Full project context
The AI doesn't guess or ask you to repeat yourself – it reads your docs, tasks and sprints and already knows what you mean.
Safe by default
The AI can't go off script. Every action is scoped by permissions and lands in the audit history.
What your AI can do inside tam.
Here's what tam already does over MCP. Some tools are still private-preview only; the full list ships with the hosted release.
Working with tasks
Create tasks, bugs and stories, change statuses, assign owners, and leave comments.
Working with knowledge
Search and read docs and wiki pages – the AI understands the project's context right away.
Connected to your code
Check PR status and link commits to tasks in GitHub.
Sprints & backlog
Plan sprints, groom the backlog, and reorder priorities – no switching to a separate tool.
Automation
Set up rules that fire themselves on an event – no code required.
Time tracking
Log time against a task and build workload reports right from the chat.
Works with the AI you already use.
Claude connects today. ChatGPT, Codex and other clients are going through security and permissions testing before the hosted release.
Access is exactly what you allow – nothing more.
Every AI agent gets its own name and limited permissions, like a new person joining the team. The foundation already works; a self-serve panel to configure it is in private preview.
Release bot
Access configured manually
What if it breaks something? The agent can't go beyond the permissions it was granted. You can revoke access at any time, with no impact on the rest of the team.
How to connect
Create an access
Set up a dedicated account for your AI agent with the access level it needs – like onboarding a new hire.
Copy the config
tam generates a ready-to-use connection file – nothing to assemble by hand.
Connect it to your AI
Add the config to Claude or another MCP client – the agent is ready to work.
tam is requesting access to your workspace's tasks, docs, and sprints

Give your AI access to your tasks today.
Connect tam over MCP through Claude and try next-generation project management.