Liminate Authoring MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIMINATE_API_KEY | No | API key for Liminate platform, required only for the translate tool |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_agreementA | 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. |
| explain_clauseB | Explain each clause of a Liminate Agreement in plain English: verb, condition, rationale, temporal window (active/expired/future/unbounded), and any unless-exception. |
| draft_agreementA | 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. |
| test_agreementB | Run a Liminate Agreement against sample evidence and return the decision: blocked, incomplete (missing evidence), needs_review, or passed. |
| list_templatesA | List the four vendored Liminate Agreement templates (id, name, purpose, agreement source, and sample evidence). |
| translateA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.