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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rmichaelthomas/liminate-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server