Documents
The context your team and your agents work from.
Specs, decisions and runbooks in pages that link both ways with your tasks, carry threaded discussions and update live. Your AI agents read and write the same pages over MCP.
Why Documents
AI writes the code. It can’t guess the why.
Agents move fast and forget everything between sessions; people forget too, just slower. Documents keep the decisions, constraints and plans next to the tasks they explain, in Markdown both can read, so every session starts from what the team already knows.
- 01
Write it once
The spec, the decision and the runbook live in one page, not scattered across chat threads and someone’s notes.
- 02
Link it where it matters
@ the page from the task and the task from the page. Each lists the other, one click apart, for as long as the work lasts.
- 03
Hand it to your agents
Claude, Cursor and other MCP clients connect at https://mcp.ontrama.com/mcp, read the context they need and keep it current, without overwriting anyone’s newer edit.
Linked both ways
The spec finds its tasks. The task finds its spec.
Mention a task in a page, or a page in a task, and both remember. No more hunting for the doc that explains a card, or the cards a decision created.
@ links to tasks and pages
Type @ to link a person, a page or a task. Links show as chips with the task’s status and open right where you are.
Mentioned in
Every page and task lists what links to it, so the spec finds its tasks and the task finds its spec.
Discussed in place
Talk it through on the sentence that matters.
Comments sit next to the page, anchored to the passage they’re about. Threads keep the back-and-forth together, and resolving one keeps the page clean.
Threads on the passage
Select a sentence and comment on it. Reply in the thread, resolve it when it’s settled, reopen it if it isn’t.
Only the pings that matter
Mentions, replies and new threads on your pages arrive in your Inbox, and by e-mail if you want them.
Live
Write together without stepping on each other.
Everyone on the page sees the others and their edits as they land. Saves are versioned, so two people typing at once never silently lose a word.
Live, with presence
See who’s on the page and watch their edits arrive. While you type, theirs waits behind a quiet bar instead of moving your cursor.
Never lose a word
Every save is versioned. If two people change a page at once, you choose what to keep, and your text is copied first.
For AI agents
Give your agents the same context you have.
Connect Claude, Claude Code, Cursor or any MCP client once, approve the access in your browser, and your agents search, read, write and comment on pages as you, with exactly your access.
Try asking
- “Read the Release plan and open a task for each unchecked item, linked from the page.”
- “Write a spec page for ACME-42 from its comments and link it to the task.”
- “Append today’s decisions to the Architecture notes page.”
Everything in Documents
Small on purpose, complete where it counts.
No setup and nothing to configure: open the workspace, press New page and write.
Pages that nest
Specs, decisions, runbooks and meeting notes as pages in the workspace, nested as deep as you need, in a tree beside your boards.
@ links to tasks and pages
Type @ to link a person, a page or a task. Links show as chips with the task’s status and open right where you are.
Mentioned in
Every page and task lists what links to it, so the spec finds its tasks and the task finds its spec.
Threads on the passage
Select a sentence and comment on it. Reply in the thread, resolve it when it’s settled, reopen it if it isn’t.
Live, with presence
See who’s on the page and watch their edits arrive. While you type, theirs waits behind a quiet bar instead of moving your cursor.
Never lose a word
Every save is versioned. If two people change a page at once, you choose what to keep, and your text is copied first.
Markdown in and out
Slash commands for headings, lists, checklists, quotes, code and images. Copy any page as Markdown, or print it.
Share by link
Publish a page read-only to anyone with the link, and take it back with one switch.
Found in a keystroke
⌘K finds pages by title and text across your workspaces, accents and all, next to your boards and tasks.
Archived, not gone
Archive a page with everything under it, and restore it from the documents home when you need it back.
Only the pings that matter
Mentions, replies and new threads on your pages arrive in your Inbox, and by e-mail if you want them.
In the API and over MCP
Everything here is in the HTTP API, and AI agents search, read, write and comment on pages over MCP, with your access.
Questions
About Documents.
What people ask before they move their docs in.
Is Trama a Notion alternative?
For the documents that go with your work, yes: nested pages, Markdown with slash commands, @links, threaded comments, live editing and public links, right beside your boards and linked both ways with your tasks.
Trama doesn't try to be a database builder or a company-wide wiki. It keeps a team's tasks and the writing behind them in one place, for people and AI agents alike.
How do documents and tasks link?
Type @ in a page, a task or a comment and pick a person, a page or a task. Pages and tasks are stored as ordinary Markdown links, so they survive copy and paste and read well to agents.
Whatever you link to lists you under “Mentioned in”: a task shows the specs that mention it, and a page shows the tasks and pages that point to it.
Can AI agents edit documents without overwriting people?
Yes. Agents connected over MCP list, search, read, create and update pages and comment in threads, acting as you with your access.
Every save carries the version it was based on. An agent that appends text builds on the latest version; one that replaces a page based on an older version is refused and handed the current text to merge, so a person's newer edit is never lost.
Who can see a page?
Pages are shared with the whole workspace, except ones kept private to the person who wrote them. Members and admins create, edit, move and archive pages; viewers read and comment.
Publishing a page gives a read-only link that works for anyone, signed in or not, until you unpublish it.
Can I bring my existing docs?
Pages are Markdown, so anything you have in Markdown moves over as it is: create pages through the API, or ask an agent over MCP to bring a folder of notes in and link them to the right tasks.
Write it down where the work is.
Documents come with every workspace. Sign in with your e-mail and start your first page.
Start with your e-mail