The Liminate Authoring MCP server helps AI agents author, validate, test, and understand Liminate Agreements — structured governance documents that control what agents are permitted to do.
validate_agreement: Parse and semantically check a Liminate Agreement, returning parse/semantic errors, unbound evidence references, and a per-rule deontic analysis (permit/forbid/require/define).
explain_clause: Break down each clause into plain English, detailing the verb, condition, rationale, temporal window (active/expired/future/unbounded), and any exceptions.
draft_agreement: Assemble a new Agreement from structured rules (verb, condition, reason, unless, starting, until) or retrieve a vendored template by ID. Output is always validated before being returned.
test_agreement: Run an Agreement against sample evidence to get a decision: blocked, incomplete (missing evidence), needs_review, or passed.
list_templates: Discover available vendored templates (e.g., EDGAR revenue check, quarterly earnings brief, publication review, student assignment review, vendor invoice review), including their source and sample evidence.
translate (paid, requires LIMINATE_API_KEY): Convert a compliance document (plain text, markdown, or URL) into an Agreement draft via the Liminate platform API, returning a fidelity manifest for human review before any installation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Liminate Authoring MCP validate my agreement file agreement.limn"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Help your AI agent author the Agreements that govern it.
Part of the Liminate family — trust infrastructure for autonomous AI, built on a 61-word prose-as-syntax language.
liminate-mcp is a standalone MCP server that lets AI agents validate, explain, draft, and test Liminate Agreements — and translate compliance documents into Agreement drafts via the Liminate platform. It never installs an Agreement. Installation onto an enforcement surface (like ~/.seshat/agreement.limn) is always a human or Seshat-governed action, never this server's.
Repo | What it does | |
Local agent harness. Enforces Agreements deny-by-default. | ||
The language and interpreter. 61 words, deterministic execution, domain packs. | ||
Semantic verification harness. Deterministic claim-verification correction loop. | ||
← this repo | Authoring MCP server. Helps an agent write the Agreements that govern it. |
Related MCP server: doc-version-mcp
Five tools run entirely on your machine, against the local liminate interpreter — no network calls, no account required:
Tool | Cost | What it does |
| free | Parse and semantically check an Agreement. Errors vs. unbound evidence references, annotated separately. |
| free | Plain-English explanation per clause: verb, condition, rationale, temporal window, exception. |
| free | Assemble an Agreement from structured rules, or return a vendored template. Always validates its own output. |
| free | Run an Agreement against sample evidence; returns a decision ( |
| free | The five vendored Agreement templates: EDGAR revenue check, quarterly earnings brief, publication review, student assignment review, vendor invoice review. |
One tool calls the platform:
Tool | Cost | What it does |
| paid | Converts a compliance document (text/markdown/url) into an Agreement draft via the |
Requires Python 3.11+.
pip install liminate-mcpOr from source:
git clone https://github.com/rmichaelthomas/liminate-mcp.git
cd liminate-mcp
pip install -e ".[dev]"
pytest{
"mcpServers": {
"liminate-authoring": {
"command": "liminate-mcp"
}
}
}Set LIMINATE_API_KEY in your environment (or the MCP client's env block) to use translate. The five local tools work with no key and no network access.
Apache 2.0. See LICENSE.
The interpreter is the trust root. Every draft is validated before it's handed back — never installed, never assumed.
Assemble a Liminate Agreement from structured rules (verb/condition/ reason/unless/starting/until), or return a vendored template by template_id. Always validates the drafted source against the interpreter before returning — never claims a draft is valid without confirming it.
Inputs: about, rules, template_id.
Explain each clause of a Liminate Agreement in plain English: verb, condition, rationale, temporal window (active/expired/future/unbounded), and any unless-exception.
Inputs: source (required).
List the four vendored Liminate Agreement templates (id, name, purpose, agreement source, and sample evidence).
Inputs: no named parameters.
Run a Liminate Agreement against sample evidence and return the decision: blocked, incomplete (missing evidence), needs_review, or passed.
Inputs: source (required), evidence (required).
PAID — convert a compliance document (source_kind: text/markdown/url) into a Liminate Agreement draft via the liminate.dev Translate API. Requires LIMINATE_API_KEY (get one at liminate.dev/keys); bills against that account. Always present the returned fidelity manifest to the user and warn them to review the draft before installing it — it controls what agents can do on their machine.
Inputs: source_kind (required), url, text.
Parse and semantically check a Liminate Agreement. Returns parse/semantic errors and a per-rule deontic analysis (permit/forbid/require/define), annotating unbound evidence references separately from genuine errors.
Inputs: source (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a distinct purpose: drafting, explaining, listing templates, testing, translating, and validating. There is no overlap or ambiguity in their functions.
Most tools follow a verb_noun pattern (e.g., draft_agreement, explain_clause), but 'translate' is a single verb without a noun, deviating slightly from the convention.
With 6 tools covering creation, validation, testing, explanation, template listing, and document translation, the count is well-scoped for an authoring server.
The set covers core authoring operations but lacks tools for retrieving or managing existing agreements (e.g., list_agreements, get_agreement), leaving a notable gap in the lifecycle.
Deterministic compliance and vertical knowledge bases for autonomous agents. Free 24hr trial.
Document creation, signing requests, and approval workflows for AI agents over Streamable HTTP.
Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits.
Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits.
