agent-spreadsheet


agent-spreadsheet is the tool interaction service for agent-based spreadsheet usage.
It gives agents a safe, inspectable, token-efficient way to read, analyze, mutate, verify, and operationalize Excel workbooks without falling back to brittle UI automation.
If you want an agent to work with spreadsheets like a real system instead of a screenshot puppet, this is the stack.
What this project is
agent-spreadsheet ships a unified spreadsheet interaction layer across three surfaces:
| Surface | Binary / Package | Mode | Best for |
|---|
| CLI | agent-spreadsheet / asp | Stateless | One-shot reads, safe edits, pipelines, CI, agent tool calls |
| MCP server | agent-spreadsheet-mcp | Stateful | Multi-turn agent sessions, workbook caching, fork/recalc workflows |
| TypeScript SDK | agent-spreadsheet-sdk | Library | App integrations β drives the server's canonical /v1 route, or runs fully in-process via the embedded WASM engine (no server required) |
The WASM build (agent-spreadsheet-wasm) is the SDK's local runtime, not a separate product surface: JS and TypeScript code targets one object model and the execution substrate (server vs embedded engine) is a configuration choice.
Supported workbook modes:
.xlsx / .xlsm β read + write
.xls / .xlsb β discovery/read-oriented workflows only
Powered by Formualizer
Every computed value in this stack comes from Formualizer β a permissively licensed (MIT/Apache-2.0) spreadsheet engine written in Rust: formula parsing, dependency-graph recalculation, 400+ Excel functions, dynamic arrays, and deterministic evaluation built for agents. No Excel COM, no headless LibreOffice.
That native engine is why this project can offer what most spreadsheet tooling for agents cannot: recalculate the actual workbook, trace which cells changed and why, and prove it β not just read cached values or push blind edits.
Embedding spreadsheet logic in your own product rather than driving workbooks as an agent? Use Formualizer directly (Rust, Python, JS/WASM).
Why agents use agent-spreadsheet
Built for tool use, not just humans
- deterministic JSON contracts
- schema and example discovery from the CLI itself
- explicit pagination and compact output modes
- machine-readable warnings and error envelopes
Safe mutation, not blind mutation
- dry-run first workflows
- stateless output modes and overwrite safety
- event-sourced session editing
- verification surfaces for proving downstream outcomes
- structural impact analysis before risky workbook changes
Spreadsheet-aware, not generic file editing
- region detection
- table and footer-aware append helpers
- template row / row band cloning
- formula-specific replace and diagnostics
- named range CRUD
- recalculation + diff + proof flows
Good agent ergonomics
- nested command groups with legacy alias compatibility
- token-efficient reads
- exact-cell inspection and layout inspection
- workflow helpers for the repetitive parts agents usually get wrong
What is new / what makes this stack different
The current surface is much stronger than a plain βread some cellsβ tool. Major capabilities now include:
asp as the primary CLI with agent-spreadsheet preserved as a compatibility alias
- grouped verification via
asp verify proof and asp verify diff
- preview-first workflow helpers for:
write append
write clone-template-row
write clone-row-band
- formula-safe batch workflows with parse-policy diagnostics
- cell/layout/export/import inspection surfaces
- named range management (
write name define|update|delete)
- formula-only replacement (
write formulas replace)
- event-sourced session editing with log, branch, undo/redo, fork, apply, and materialize
- SheetPort manifest lifecycle + execution for contract-driven spreadsheet automation
Install
Shell installer
curl -fsSL https://raw.githubusercontent.com/PSU3D0/agent-spreadsheet/main/install.sh | sh
The installer downloads a prebuilt CLI to ~/.local/bin and creates the asp command. Pin a release with ASP_VERSION=0.15.0, set ASP_INSTALL_DIR to choose another destination, or pass --mcp to install the MCP server too:
curl -fsSL https://raw.githubusercontent.com/PSU3D0/agent-spreadsheet/main/install.sh | sh -s -- --mcp
npm
npm i -g agent-spreadsheet
This installs both asp (the primary command) and agent-spreadsheet (the compatibility alias) from a prebuilt native binary. No Rust toolchain is required.
cargo-binstall
cargo binstall agent-spreadsheet
This installs the prebuilt CLI in seconds.
Cargo
cargo install agent-spreadsheet --features recalc --bin asp --bin agent-spreadsheet
This builds the CLI from source. Formualizer (the native Rust recalc engine) is included by default.
mise
mise use -g "ubi:PSU3D0/agent-spreadsheet[exe=asp]"
# Homebrew
brew install psu3d0/tap/agent-spreadsheet
MCP server
cargo install agent-spreadsheet-mcp
Docker
# Read-only / slim
docker pull ghcr.io/psu3d0/agent-spreadsheet-mcp:latest
# Write + recalc + screenshots
docker pull ghcr.io/psu3d0/agent-spreadsheet-mcp:latest-full
JavaScript SDK
npm i agent-spreadsheet-sdk
Prebuilt binaries
Download raw binaries and archives from GitHub Releases.
Published native assets include:
- Linux x86_64
- Linux arm64
- macOS x86_64
- macOS arm64
- Windows x86_64
Start here: the core workflows
1) Orient the workbook before reading cells
# What sheets are here?
asp read sheets data.xlsx
# What regions/tables/parameter blocks does this sheet contain?
asp read overview data.xlsx "Model"
# What named items are available?
asp read names data.xlsx
# Read a structured region as a table
asp read table data.xlsx --sheet "Model"
2) Inspect exactly what an agent needs
# Raw values for exact ranges
asp read values data.xlsx Model A1:C20
# Detail-view for targeted cells (value / formula / cached / style triage)
asp read cells data.xlsx Model B2 D10:F12
# Layout-aware rendering for a bounded range
asp read layout data.xlsx Model --range A1:H30 --render both
# Export a bounded range to csv or grid json
asp read export data.xlsx Model A1:H30 --format csv --output model.csv
3) Do a safe stateless edit β recalc β proof β diff loop
asp workbook copy data.xlsx /tmp/draft.xlsx
asp write cells /tmp/draft.xlsx Inputs "B2=500" "C2==B2*1.1"
asp workbook recalculate /tmp/draft.xlsx
asp verify proof data.xlsx /tmp/draft.xlsx --targets Summary!B2,Summary!B3 --named-ranges
asp verify diff data.xlsx /tmp/draft.xlsx --details --limit 50
A representative label-mode lookup:
asp analyze find-value data.xlsx "Net Income" --mode label --label-direction below
4) Preview structural risk before mutating the workbook
asp analyze ref-impact data.xlsx --ops @structure_ops.json --show-formula-delta
This is intentionally read-only. It surfaces shifted spans, absolute-reference warnings, token counts, and optional before/after formula samples.
5) Use workflow helpers instead of reinventing row logic
# Stateless batch writes
asp write batch transform data.xlsx --ops @ops.json --dry-run
asp write batch style data.xlsx --ops @style_ops.json --dry-run
# Append rows into a detected region or table, respecting footer rows when present
asp write append data.xlsx --sheet Revenue --table-name RevenueTable --from-csv rows.csv --header --dry-run
# Clone one template row with preview-first planning
asp write clone-template-row data.xlsx --sheet Inputs --source-row 8 --after 8 --count 3 --dry-run
# Clone a contiguous row band repeatedly
asp write clone-row-band data.xlsx --sheet Forecast --source-rows 12:16 --after 16 --repeat 4 --dry-run
6) Use a stateful session when the edit story gets complex
asp session start --base data.xlsx --workspace .
asp session op --session <id> --ops @edit.json --workspace .
asp session apply --session <id> <staged_id> --workspace .
asp session materialize --session <id> --output result.xlsx --workspace .
And when you need proper history and branching:
asp session log --session <id> --workspace .
asp session fork --session <id> scenario-a --workspace .
asp session undo --session <id> --workspace .
asp session redo --session <id> --workspace .
asp session checkout --session <id> <op_id> --workspace .
7) Turn workbook interfaces into contracts with SheetPort
# Discover candidate ports from workbook structure
asp sheetport manifest candidates model.xlsx
# Validate or normalize a manifest
asp sheetport manifest validate manifest.yaml
asp sheetport manifest normalize manifest.yaml
# Bind-check a workbook against a manifest
asp sheetport bind-check model.xlsx manifest.yaml
# Execute the manifest with JSON inputs
asp sheetport run model.xlsx manifest.yaml --inputs @inputs.json
CLI overview
The primary CLI is asp.