weave

<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="brand/assets/png/weave-loader-dark.gif"> <img src="brand/assets/png/weave-loader-light.gif" alt="weave logo — two strands weaving into the mark" width="240"> </picture> </p> <h1 align="center">weave</h1> <p align="center"> <strong>An open-source, self-hosted alternative to Airtable, Fibery, Notion databases, and ClickUp — built so that AI agents are first-class users, not an afterthought.</strong> </p> <p align="center"> Connected tables, relations, workflows, formulas, rollups, and per-entity markdown documents. One SQLite file. Zero dependencies. No build step. MIT. </p> <p align="center"> <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-blue.svg"></a> <img alt="Node &gt;= 22.16" src="https://img.shields.io/badge/node-%E2%89%A5%2022.16-3c873a.svg"> <img alt="Runtime dependencies: 0" src="https://img.shields.io/badge/runtime%20dependencies-0-brightgreen.svg"> <img alt="Self-hosted" src="https://img.shields.io/badge/self--hosted-yes-blueviolet.svg"> <img alt="MCP server included" src="https://img.shields.io/badge/MCP-server%20included-8a63d2.svg"> </p> <p align="center"> <a href="#for-agents">For agents</a> · <a href="#quickstart">Quickstart</a> · <a href="#how-weave-compares">Comparison</a> · <a href="#agents-mcp-rest-and-cli">Agents &amp; MCP</a> · <a href="#self-hosting">Self-hosting</a> · <a href="#faq">FAQ</a> </p> <p align="center"> <img src="docs/screenshots/table.png" alt="weave table view — a connected table with workflow state chips, milestones, and per-row documents" width="900"> </p>

---

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 <file.db>, the same as weave mcp --data <file>. 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 <spec.json> --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 platform you run yourself: spaces hold tables, tables hold entities, and entities connect to each other through real bidirectional relations — with lookups, rollups, formulas, workflow states, automations, and any number of markdown documents attached to each row.

It is meant to replace the SaaS your work already lives in — Airtable's bases and grids, ClickUp's tasks and boards, Fibery's connected databases with documents and automations — running on your laptop or your own server, with no per-seat bill and no vendor holding the export button.

The difference from every other tool in this category is the second audience. Work-management tools are built for humans first and APIs second. weave is built for humans and agents as equals: everything the web UI can do, the REST API, the CLI, and the built-in MCP server can do too — same engine, same data file on your disk. No signup, no cloud, no telemetry.

• Local-first — your workspace is one SQLite file next to your project.
• Yours to host — one Node process and one file; run it on a laptop or a small VPS behind your own TLS and login (see Self-hosting).
• Zero dependencies — git clone and run. Storage is Node's built-in node:sqlite; the only third-party code is vendored and pinned.
• Agent-native — an MCP server any stdio client can mount (Claude Code, Codex CLI, Cursor, Gemini CLI), a scriptable CLI, Table#12 refs everywhere, and markdown documents addressable as plain URLs (/e/Task#12/doc.md, .html, .pdf).
• Undoable — every entity mutation (edits, creates, deletes, links, comments) can be stepped back with weave undo, POST /api/undo, or the weave_undo MCP tool; agents get to make mistakes without making a mess.
• 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

Open http://127.0.0.1:4400 — 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. Stars are how the agent scouts and the directories 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 a sign-in provider (Door C) is one line too. The first call opens the provider's sign-in in your browser; no token to paste:

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

/w/<name>/mcp serves another workspace. Your account has to be linked to your provider sign-in first (open the invite weave account link <name> prints, once, in a browser), and it needs the Architect role, since MCP carries the schema tools.

Sixteen tools by default, the ones a workspace build uses, weave_build among them, plus weave_call, which reaches the other forty-four. weave mcp --tools all (or WEAVE_MCP_TOOLS=all) lists all 60. The same undo the UI has, and weave_vocabulary so an agent reads the allowed values instead of guessing. Full map: Agents: MCP, REST, and CLI.

Screenshots

| Documents on every row | Relation map | Universal search | | --- | --- | --- | | <img src="docs/screenshots/document.png" alt="weave entity page — a markdown document rendered beside the entity's fields" width="290"> | <img src="docs/screenshots/map.png" alt="weave relation map — tables connected by relations with the automation layer drawn in" width="290"> | <img src="docs/screenshots/search.png" alt="weave command-K search palette showing cross-workspace results with copyable permalinks" width="290"> | | Every entity carries markdown documents, addressable as .md, .html, and .pdf URLs. | The schema, drawn: relations with cardinality, plus the automation layer. | ⌘K across every workspace, backed by SQLite FTS5, with copyable permalinks. |

<img src="docs/screenshots/dock.png" alt="weave table with one row opened in the dock beside it, the breadcrumb on one line above the table toolbar" width="900">

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

| | weave | Airtable | ClickUp | Fibery | | --- | --- | --- | --- | --- | | License | MIT, open source | Proprietary | Proprietary | Proprietary | | Where the data lives | A .db file you own | Vendor cloud | Vendor cloud | Vendor cloud | | Pricing | Free — it's a repo | Per seat, per month | Per seat, per month | Per seat, per month | | Row / record caps | Your disk | Plan-tiered | Plan-tiered | Plan-tiered | | Agent access | MCP server + REST + CLI, all first-class | API + partner integrations | API + partner integrations | API + partner integrations | | Runs offline | Yes | No | No | No | | Telemetry | None | Vendor-defined | Vendor-defined | Vendor-defined |

Against other open-source Airtable 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:

| Project | License | Install shape | Optimized for | | --- | --- | --- | --- | | weave | MIT | One Node process, one file, no deps | Agent access, connected documents, disappearing into a repo | | NocoDB | Sustainable Use License (since v0.301.0) | Docker + external DB | Putting a smart-spreadsheet UI on an existing MySQL/Postgres | | Baserow | MIT (core; paid tiers separate) | Docker Compose + Postgres | A full Airtable-shaped product, cloud or self-hosted | | Grist | Apache-2.0 | Docker or Node | Spreadsheet-grade formulas and data analysis | | Teable | AGPL-3.0 (core) | Docker + Postgres | Postgres-native scale with an Airtable UI |

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. Pick one of the others if you need multi-user permissions, a hosted option, or a mature plugin ecosystem — see what weave is not.

What's inside

| Area | Details | | --- | --- | | Data model | Spaces → tables → entities. Field types: text, number, rating (icons you click to fill, 0 to a max), date, date range, checkbox, toggle (a switch with two named states), url, email, select, multiselect, workflow states, bidirectional relations, lookups, rollups (count, sum, avg, median, min, max, range, stdev, distinct, filled, empty, join — over a relation, or over a whole table from the space's own row, which is what the grid footer draws), formulas, and any number of markdown document fields per entity. | | Statistics | weave stats <table> (also weave_stats and GET /api/tables/:ref/stats): every column summarised — five-number summary, stdev and a histogram for numbers, ranked distributions for chips, earliest/latest/span for dates — grouped with --by, narrowed with --where. | | Views | Table, entity pages (docked beside the table or opened full page), a relation map with the automation layer drawn in, and per-space/table filtering. Inline editing everywhere. | | Documents | Every doc is a native URL: .md, .mmd, .html, .pdf. Mermaid diagrams, raw HTML and math render in place; [[Table#12]] mentions resolve to links. Whole-entity export paginates one page per document. Math is KaTeX only ($…$ / $$…$$, vendored + offline); the other fence engines Vditor knows (graphviz, echarts, plantuml, mindmap, abc, flowchart) are deliberately not vendored, so those fences stay plain code blocks. | | Automations | Triggers (created / field changed / state changed) → set field, append doc, add comment, outgoing webhook. | | Search | Universal ⌘K across workspaces with copyable permalinks, backed by a SQLite FTS5 index. | | Storage | One workspace = one .db file (WAL, row-level writes, crash-safe). Legacy JSON workspaces migrate automatically; exportJSON/importJSON remain the human-readable interchange. CLI, server, and MCP can run concurrently. | | Interfaces | Web UI (vanilla JS, no build step) · REST API · CLI (bin/weave.js) · MCP server (weave mcp). |

Agents: MCP, REST, and CLI

Every interface drives the same engine and the same file. Nothing is UI-only.

MCP — point any MCP client at the stdio server. Claude Code, Claude Desktop, Codex CLI, Cursor, Gemini CLI, Windsurf and OpenCode all mount stdio servers, so one config block works in each of them:

{
  "mcpServers": {
    "weave": {
      "command": "node",
      "args": ["/path/to/weave/bin/weave.js",