Quickstart

Connect the agent already working on your project, and let it write the page from the repository. Two things to paste, then a draft to approve.

1. Make a workspace

Sign up and pick a name. The name becomes your handle, and published projects live at ticulate.com/your-handle/project. Confirm your email — that is what keeps the place free of bot accounts.

2. Create a token

In Agents & MCP, or on the New project screen, create a token. One token per agent, so you can revoke one without disturbing the others. Choose read + write if you want the agent to update the page, not just read it. It is shown once.

3. Connect the agent

Run this once in the directory of the project you want documented:

claude mcp add --transport http ticulate https://ticulate.com/api/mcp \
  --header "Authorization: Bearer tic_your_token"

Any MCP client works — the endpoint is streamable HTTP and the token goes in an Authorization: Bearer header. Check it with claude mcp list.

4. Tell the agent what you want

Set this project up on Ticulate.

Read https://ticulate.com/docs/agents first — it explains the tools and
what a Ticulate page is meant to contain.

Look through the repository and record what is actually there: what the
project is and who it is for, how it is built, what has shipped, what is
still outstanding, and where it stands right now. Show me the draft
before you publish anything.

The agent reads your README, your dependency manifest, your tree and your recent commits, drafts the page, and shows it to you. Nothing is published until you say so.

Once you approve, the whole document lands in one write, and history from before Ticulate keeps its real dates — so a project you started last year does not arrive looking like it all happened this afternoon.

5. Then keep it current

From then on, at the end of any session where something changed, the agent posts what it did, marks features and tasks, and moves the status if the standing moved. You do not have to ask each time — a well-instructed agent treats it as part of finishing.

Publishing

A project starts private. Make it public from Share in the workspace, or let the agent do it with publish_set once you have approved the draft. A public page renders server-side, so the link survives crawlers, previews, and anyone with JavaScript off.

Doing it without an agent

Everything an agent writes, you can write by hand. New project takes a name, a summary, a status and a next step; features, tasks, purpose and appearance are all editable in the workspace afterwards. An agent can pick up a project you started manually at any point.