Local-first · File-backed · MCP-native
The workspace you bring your agent to.
Worktable is a shared workspace where humans and AI agents create, organize, and reuse durable work artifacts — documents, live widgets, and file-backed records that outlast the conversation.
Works with Claude Code, Claude Desktop, Cursor — any MCP client.
Files are the protocol.
Your workspace is a folder you pick. Docs are markdown. Records are YAML. Widgets are HTML. Everything humans and agents make together sits on your disk in formats you can read without us.
- Portable
The folder is the workspace. Move it, back it up, open it anywhere — there is no export, because it never stopped being files.
- Versioned your way
git init it, sync it, snapshot it. Docs carry their own history; the rest is plain files under whatever discipline you already use.
- Agent-greppable
Any tool that reads files can work the workspace — your agent doesn't need permission from a database to be useful.
Four primitives. One shared surface.
Chat produces answers that evaporate. Worktable gives the work somewhere to live: artifacts you and your agents keep creating, finding, editing, and reusing.
Docs
Versioned documents — markdown or rich blocks. Drafted by you, expanded by your agent, with full history either way.
Widgets
Self-contained HTML mini-apps in a sandboxed runtime. Dashboards, trackers, briefings, prototypes — agents build them, humans use them.
Records
File-backed YAML collections: durable structured state both sides can query and update, instead of re-deriving it every session.
Annotations
Comments and instructions attached to anything in the workspace — the channel where humans direct agents and agents report back.
Any agent. One connection.
No bundled assistant, no proprietary runtime. Worktable is a place your agent works, whatever your agent is.
- 1Connect
One MCP config in Claude Code, Claude Desktop, Cursor, or any MCP client. Local agents get stdio with zero ceremony; remote ones get scoped tokens.
- 2It learns the house rules
Skill docs ship with the workspace — your agent reads them on arrival and knows how docs, widgets, records, and annotations work before its first edit.
- 3It notices
Outbound events — annotation created, doc changed, record updated — mean your agent reacts to the workspace instead of polling it. Leave an instruction at lunch; find it handled.
{
"mcpServers": {
"worktable": {
"command": "worktable",
"args": ["--mcp"]
}
}
}That's the whole integration. Remote and hosted workspaces connect over HTTP with a token instead.
Runs where you do.
One core, three shapes. The workspace that runs on your laptop is the same one we host — not a downgrade and an upsell.
Local
One command. The server starts, your browser opens, your workspace lives in a folder you chose. Free, forever, fully yours.
Local Server
The same core on a machine you control: scoped access tokens, your phone in the workspace, agents that stay on while your laptop sleeps.
Worktable Cloud
A managed instance we run for you — synced with your local workspace, backed up, shareable, ready for your team. Your files stay canonical.
Local is private. Cloud is convenience.
Local Worktable gives you a portable workspace on your machine. Worktable Cloud adds sync, sharing, backups, and teams without changing the way your workspace works.
Local
The full core, on your machine.
- Every primitive, unlimited spaces
- Unlimited connected agents
- Your folder, your files, no account
Cloud Solo
Your workspace, everywhere.
- Managed instance, zero setup
- Local ↔ cloud sync and backups
- Publish docs and widgets with a link
Cloud Teams
Shared spaces for humans and agents.
- Team spaces with roles and permissions
- Scoped per-agent access tokens
- Admin controls and audit trail