weave

weave

weave is an open-source, self-hosted work database and Airtable alternative. People use the web UI and AI agents use the built-in MCP server, REST API or CLI, on the same tables.

It replaces Airtable, Fibery, Notion databases and ClickUp with connected tables, relations, workflows, formulas, rollups, kanban boards, forms and markdown documents on every row. One SQLite file. Zero dependencies. No build step. MIT.

For agents · Quickstart · Comparison · Agents & MCP · Self-hosting · FAQ

---

For agents

weave stores structured work (tables, rows, relations, documents) in one SQLite file, and an agent drives it over MCP, REST or the CLI.

• Connect over MCP: node bin/weave.js mcp --data , the same as weave mcp --data . In Claude Code: claude mcp add weave -- node /path/to/weave/bin/weave.js mcp --data /path/to/workspace.db
• Or build from a file: weave build --dry-run, then again without --dry-run.
• Read AGENTS.md › Using weave first: the primer, every tool by job, plans with turn budgets, and common errors with their fixes.

What weave is

weave is a work database you run yourself. Spaces hold tables, tables hold rows (the API calls them entities), and rows link to each other through bidirectional relations, with lookups, rollups, formulas, workflow states, automations and any number of markdown documents on each row.

It replaces the SaaS your work already lives in: Airtable bases and grids, ClickUp tasks and boards, Fibery's connected databases with documents and automations, and Notion databases. It runs on your laptop or your own server, with no per-seat bill and no vendor holding the export button.

weave is built for people and AI agents as equals: everything the web UI can do, the REST API, the CLI and the built-in MCP server can do too, on the same engine and the same data file on your disk. A local install needs no account and sends no telemetry.

• One file per workspace: a workspace is one SQLite file next to your project, served by one Node process on a laptop or a small VPS behind your own TLS and login (see Self-hosting).
• weave cloud: the same code runs at https://weave.grunion.ai behind a sign-in. A new account starts at /start, which sets up a workspace, a template and an agent connection. weave backup --dest weave:// / sends a self-hosted install's sealed nightly archive there (the cloud stores ciphertext only), and weave workspace migrate moves a workspace across.
• Zero dependencies: git clone and run, since storage is Node's built-in node:sqlite, and the only third-party code is vendored and pinned.
• Agent access: an MCP server any stdio client can mount (Claude Code, Codex CLI, Cursor, Gemini CLI), a scriptable CLI, row references such as Task#12 everywhere, and markdown documents addressable as plain URLs (/e/Task#12/doc.md, .html, .pdf).
• Undo: weave undo, POST /api/undo and the weave_undo MCP tool reverse any change to a row: edits, creates, deletes, links and comments.
• Versioned documents: every document field keeps its revisions (one per editing session), browsable and restorable from the page, weave doc-revisions / weave doc-restore, or the weave_doc_revisions / weave_doc_restore MCP tools.

Quickstart

Requires Node ≥ 22.16 (Node 24 LTS recommended). There is nothing to build and nothing to install from npm.

git clone https://github.com/grunion-ai/weave

cd weave node bin/weave.js serve --port 4400 --data ./my-workspace.db

Or start it in a container from the same checkout:

docker compose up -d

Or run the image each release publishes to the GitHub Container Registry. Your workspaces, attachments and keystore stay in the weave-data volume at /data:

docker run -d --name weave -p 127.0.0.1:4400:4400 -v weave-data:/data ghcr.io/grunion-ai/weave:latest

Open http://127.0.0.1:4400 and press ⌘K to search everything. A self-documenting weave docs workspace is provisioned alongside your data at /w/weave/: handbook, wiki, the public issue tracker and roadmap, and a Quality space mirroring the test suite.

If weave replaces a SaaS seat for you, star the repo so other teams can find it.

Connect your agent

One config block, any stdio MCP client (Claude Code, Claude Desktop, Codex CLI, Cursor, Gemini CLI, Windsurf, OpenCode):

{ "mcpServers": { "weave": { "command": "node",

"args": ["/path/to/weave/bin/weave.js", "mcp", "--data", "/path/to/my-workspace.db"] } } }

Or add it to Claude Code in one line:

claude mcp add weave -- node /path/to/weave/bin/weave.js mcp --data /path/to/my-workspace.db

A hosted instance with an OpenID Connect sign-in provider takes one line too. The first call opens the provider's sign-in in your browser:

claude mcp add --scope user --transport http weave https://weave.example.com/mcp

For weave cloud at weave.grunion.ai, this repository is also a Claude Code plugin marketplace. In Claude Code:

/plugin install weave --marketplace grunion-ai/weave

Each workspace on an instance has its own endpoint, /w/ /mcp. Link your account to your provider sign-in first: run weave account link , which prints a one-time invite, and open that invite in a browser. Any role connects, and tools/list names only the tools that role may call.

The server lists 17 tools by default: the 16 a workspace build uses, weave_build among them, and weave_call, which runs the other 48. weave mcp --tools all (or WEAVE_MCP_TOOLS=all) lists all 65. The 65 include the same undo the UI has, and weave_vocabulary, which returns the allowed values so an agent reads them instead of guessing. Full map: Agents: MCP, REST, and CLI.

Screenshots

Open any row and it docks beside its table, so the entity and the rows around it stay in view together.

How weave compares

Against the SaaS it replaces

Against the open-source alternatives

The open-source options in this space are all worth a look, and several are far more mature than weave. They differ mainly in what they optimize for:

*Licenses and packaging as of August 2026; check each project for current terms.* Pick weave if you want connected tables plus markdown documents plus an MCP server, with no container, no database server, and no dependency tree, and one of the others if you need permissions narrower than a workspace role or a mature plugin ecosystem (see [what w