
Jacobian
io.github.morlutoPublished by GitHub account morlutov0.23.0Updated Oct 27, 2026
Executable mathematics and independent verification for AI agents.
Overview
Jacobian gives an AI assistant a searchable vocabulary of typed math operations it can find, run and compose for exact, verifiable results.
- What you can do
- Find and inspect typed mathematical operations by need or exact contract
- Run a single bounded operation and get its typed, exact result
- Compose results by passing typed values into later operations
- Cover polynomial algebra, exact linear algebra, graphs, bounded SAT/SMT, finite algebra, probability, geometry and topology
- When to use it
- Useful when an assistant needs trustworthy, exact mathematical computation rather than free-form reasoning: determinants, gcds, graph problems, SAT/SMT checks, or stepwise composition of small verified operations.
- Requirements
- Runs locally over stdio. The setup command needs Node.js 20.17+, 22.13+ or 23.5+ and uvx on PATH; the Python server runs via uvx or pip and needs CPython 3.12 or 3.13 on glibc Linux x86-64 for the tested contract. Optional Singular and QEPCAD runtimes cover a few operations. No authentication or environment variables declared.
Installation
In SourceWeft
- Open Jacobian in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
English · 简体中文
Jacobian
An executable mathematical vocabulary for agents: discover one typed operation, run it, and compose its result.
[CI] [PyPI] [npm] [Supported Python versions] [MIT license]
Jacobian is an MCP server that gives AI agents a searchable vocabulary of typed
mathematical operations. math.find matches a mathematical need or inspects one
exact contract, and math.run executes it and returns its typed result. The same
mathematical library is also available through a CLI and native Python API.
Each operation establishes one stable, reusable mathematical postcondition rather than prescribing a workflow or proof strategy. Results are exact where claimed and make approximation, incompleteness, or uncertainty explicit.
Jacobian's hypothesis is that mathematical reasoning benefits from an executable vocabulary of semantically scoped, bounded operations. Rather than exposing large domain solvers or precomposed workflows, Jacobian exposes mathematical primitives that agents can search for and compose into solutions beyond what any individual operation was designed to solve. The library supplies trustworthy mathematical moves; the reasoning model decides which moves to make, how to combine their results, and when to stop. Keeping the operations semantically narrow and domain-owned preserves that search space instead of baking one proof strategy or workflow into the tools themselves.
See Executable mathematical vocabulary for what semantic atomicity means and how the operation vocabulary grows.
Quickstart
Set up Jacobian for your agents with a single command. The setup command
requires Node.js 20.17+, 22.13+, or 23.5+ and uvx on your PATH.
Choose detected agents and review the changes before they are written. Setup
does not install Node.js, Python, uv, or an agent. For automation, preview
an explicit plan with npx jacobian@latest setup --codex --dry-run; use
--yes only with explicit agent flags or --all.
To refresh an existing registration explicitly, run
npx jacobian@latest upgrade and select the agents to update. The generated
launcher pins the exact release resolved by npm.
Run the canonical Python MCP command without installing Jacobian globally:
Where an MCP host requires an npm command, the npm package is a deterministic carrier for that same command:
For a persistent installation:
That package includes Jacobian's exact maintained Python backend stack: SymPy, NetworkX, Z3, and Python-FLINT. A normal Python or npm installation therefore exposes the same built-in Python-backed operation portfolio. The tested binary-install contract is CPython 3.12 or 3.13 on glibc Linux x86-64; the release gate installs the built wheel and starts Jacobian on both Python versions. Other systems may have compatible upstream wheels, but are not part of the tested release contract yet. In particular, Alpine/musl cannot install the complete mandatory stack from PyPI.
Singular and QEPCAD are optional system runtimes for a small subset of operations.
The Python installation does not provision them, and ordinary operations do not
require Docker. Python callers can use jacobian.backends.check_backend; MCP
inspection reports availability in the server environment. See
backend requirements for exact coverage
and setup.
The Python distribution contains the mathematical kernel, CLI, and MCP server.
The npm package deterministically maps its exact package version to the
corresponding uvx invocation.
Compute one bounded result
An ordinary operation returns mathematics first. For example,
matrix.determinant.compute accepts one exact rational matrix and returns its
determinant directly. Callers compose results by passing their typed values to a
subsequent operation.
For a local terminal workflow, inspect the exact installed contract and run one of its examples with the CLI:
The second command returns the gcd and Bézout coefficients as JSON. In an MCP
host, use math.find in inspection mode to read the same contract and math.run
with the same payload shape. See Discover and invoke operations
for that agent workflow.
Available mathematics
The built-in portfolio covers work in:
- polynomial maps and polynomial algebra;
- exact linear algebra;
- graphs, paths, colorings, and isomorphism;
- bounded SAT and SMT solving;
- finite algebra, probability, geometry, and topology.
SAT and SMT operations use the maintained Z3 Python binding directly. Use
math.find to match the mathematical result needed, then use its inspection
mode on a promising operation before calling math.run once.
See the domain operation library for the maintained operation portfolio and backend requirements.
Status
Jacobian 0.23.0 is pre-stable. Its published package and operation contracts describe the supported surface; experimental operation contracts may change between releases.
Documentation
- Documentation home: tutorials, how-to guides, reference, and explanations
- Architecture: runtime structure and trust boundaries
- Product model: operation contracts, ownership, and project boundaries
- Tool reference: MCP resources and invocation contracts
- Backend requirements: maintained Python backends
- Remote deployment: HTTP deployment and authentication
Contributing
Jacobian uses Python 3.12, uv, and a small Makefile:
Read CONTRIBUTING.md before changing code. It documents focused test commands, verification rules, documentation placement, and pull-request expectations.
License
Source: README.md at commit bad9b89
Tools
0Version history
3- v0.23.0LatestOct 3, 2026
- v0.22.0Sep 17, 2026
- v0.21.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts