Tools

One engine, every surface. The same grammar-first engine that powers the CLI and the playground also lives in your editor, your notes, your build pipeline, and your agents — no tool re-implements a formula.

Learn by example

examples	Every language feature as a worked, runnable sheet — per-row aggregates, embedded sheets, pipes, executables, the whole function library. Each example carries a Try link that opens it in the playground, the sheet traveling entirely in the URL. Source.

In your editor

lsp	The language server for `.tsvt`: diagnostics from `check`, hover from `explain`, completion for every function — in any editor that speaks LSP. Source.
vscode	The VS Code extension: the `.tsvt` language with a TextMate grammar for highlighting, and the language server wired in as its client. Not yet published — until it is, point any generic LSP client at `tsvsheet-lsp`.
intellij	The IntelliJ plugin: `.tsvt` highlighting via TextMate, with the language server bound in through LSP4IJ — the same diagnostics and hovers in JetBrains IDEs. Not yet published.

In your notes & docs

A fenced ```sheet block renders as a computed grid wherever your Markdown is processed:

goldmark	Go markdown pipelines (Hugo and friends): server-side static tables, no client JS. Source.
remark	JS markdown pipelines: remark and markdown-it plugins over the wasm engine. Source.
obsidian	Obsidian: live ```sheet blocks in notes, plus a `.tsvt` file view for your vault. Source.
js	The web: a typed JS API and the `<tsv-sheet>` element — the engine as WebAssembly, the same build that powers the playground and the live sheets on the landing page. Source.

For agents

mcp	The MCP server: `render`, `check`, `explain`, and `eval` as tools, so agents drive spreadsheets through files they can read, edit, diff, and verify as text. Source.
claude	The Claude Code marketplace and plugin: language and LSP skills plus MCP access, so Claude works on `.tsvt` sheets with the real engine behind it. Not yet published — the MCP server above works with any MCP client today.

As a service

api	The sheet API server — the tsvsheet edit language over HTTP: a document plane, a change feed, and computed reads, so an application edits sheets over the wire with the same semantics the CLI applies to a file. Source.

As a library

go-tsvsheet	The engine as an importable Go library — parse, compute, and inspect `.tsvt` files with no CLI in sight. Source.
tsvsheet	The language home: the ANTLR4 grammar and the specification every implementation follows.

The companion isnow date/time pattern language has its own family — a Go library, a standalone CLI, a JS engine, and a playground — covered on its page.