Docs · AI agent signing

Plugin vs skill vs MCP connector

Three pieces work together when Claude (or another agent host) signs with your company certificate. None of them receives your private key — signing happens in Liminal Keys custody over MCP using a hash only.

MCP connector (remote account link)

The connector is your live link to Liminal Keys. Production URL:

https://mcp.liminalkeys.com/mcp

In Claude, you add that URL and choose Connect. Sign-in uses URL-only OAuth with automatic client registration — you do not paste a client ID or client secret. You sign in with your Liminal Keys account (the same options as Console).

The connector exposes four remote tools: list_certificates, get_certificate_chain, sign_hash (with optional human approval), and optional timestamp. Response envelopes are cryptographically signed; the skill verifies them. The private key never leaves Liminal Keys.

Skill — liminalkeys-sign 0.1.10 (local instructions + program)

A skill is agent instructions plus a small local program. The liminalkeys-sign skill tells the agent the exact steps and ships offline Python wheels and the liminal-sign helper.

  • Hash locally — for PDFs, liminal-sign prepare digests the file in the sandbox; only the 32-byte digest goes to MCP.
  • Call sign_hash on the connector (one approval on your phone or in LK Approvals when policy requires it).
  • Finish locally — liminal-sign finish embeds the signature, runs mandatory validation, and by default draws the branded visible stamp on the PDF.

Standalone zip (same bits as the plugin bundle): liminalkeys-sign-skill-0.1.10.zip (SHA-256).

Claude plugin — LiminalKeys/claude-plugin (install package)

The plugin is the installable package that wires everything up for Claude Code and claude.ai: it registers the liminalkeys-sign skill and the MCP connector settings for https://mcp.liminalkeys.com/mcp. Install or refresh from the public LiminalKeys/claude-plugin marketplace — see Claude setup on the main AI agents guide.

How they fit together

Your PDF and chain PEM stay in the agent sandbox. Only digests and MCP messages cross the network.

┌──────────────────────────── Claude (plugin installed) ────────────────────────────┐
│                                                                                   │
│   SKILL (liminalkeys-sign)          MCP CONNECTOR              YOUR LK ACCOUNT      │
│   ─────────────────────           ───────────────            ─────────────────    │
│   liminal-sign prepare  ──hash──►  sign_hash  ────────────►  Key Vault sign       │
│        │                              ▲                      (private key       │
│        │         previews             │                       never exported)   │
│        ▼                              │ approval (optional)                       │
│   liminal-sign finish ◄──signature────┘                                           │
│   embed + validate + stamp                                                          │
└───────────────────────────────────────────────────────────────────────────────────┘

What to configure where

PieceYou configureRuns where
MCP connectorMCP URL + Connect (OAuth) or optional lkag_… API key headerClaude → Liminal Keys cloud
SkillInstalled via plugin or skill zip uploadAgent sandbox (local CLI)
PluginMarketplace add + install / refresh on claude.aiClaude product
Policy & approvalsConsole → AI agents, policy rules, LK ApprovalsConsole + PWA

AI agents & MCP setup · LK Approvals · Console