Skip to main content
Glama
@actalumen/mcp-server

@actalumen/mcp-server

Official
by ActaLumen

@actalumen/mcp-server

MCP server for ActaLumen — verify documents for compliance from Claude Desktop, Cursor, and Claude Code.

What it does

Exposes ActaLumen's verification, chat, and document tooling to any MCP-compatible AI agent. Your agent can upload a contract, run it against a compliance template (SOC2, GDPR, custom), and chat with the document — all grounded in citations.

PII is redacted server-side before storage. Agents never see un-redacted content, even when explicitly asked.

Related MCP server: PII Redaction MCP Server

Install

Easiest: MCPB bundle (Claude Desktop one-click)

Download actalumen-<version>.mcpb from the latest release and double-click it. Claude Desktop will prompt for your API key and upload directory, then install. No Node, no JSON editing.

Or via npm (Cursor, Claude Code, custom MCP clients)

Prerequisites

  1. An ActaLumen API key with read, write, and verify scopes. Create one at app.actalumen.com → Settings → API Keys.

  2. Node.js 18.17 or newer.

  3. A directory the agent is allowed to upload from. Default: ~/actalumen-inbox (create it: mkdir ~/actalumen-inbox).

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "actalumen": {
      "command": "npx",
      "args": ["-y", "@actalumen/mcp-server"],
      "env": {
        "ACTALUMEN_API_KEY": "ak_live_..."
      }
    }
  }
}

Restart Claude Desktop. You should see the ActaLumen tools in the tools menu.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "actalumen": {
      "command": "npx",
      "args": ["-y", "@actalumen/mcp-server"],
      "env": { "ACTALUMEN_API_KEY": "ak_live_..." }
    }
  }
}

Claude Code

claude mcp add actalumen -- npx -y @actalumen/mcp-server
# then set the key in your shell or settings:
export ACTALUMEN_API_KEY=ak_live_...

Configuration

Env var

Default

Purpose

ACTALUMEN_API_KEY

(required)

Org-scoped API key.

ACTALUMEN_BASE_URL

https://api.actalumen.com

Override for self-hosted or staging.

ACTALUMEN_UPLOAD_DIR

~/actalumen-inbox

Path allowlist — agents can only upload files from inside this directory.

Tools

Tool

Purpose

upload_document

Upload a PDF (must be inside ACTALUMEN_UPLOAD_DIR). Returns a document ID; PII is redacted on the server before storage.

get_document

Poll a document's status — wait for READY before verifying or chatting.

list_documents

Find existing documents by name without re-uploading.

list_templates

Discover available compliance templates (e.g., SOC2 Vendor).

start_verification

Run a document against a template. Returns a jobId.

get_verification

Fetch report status and findings.

chat_with_document

Ask grounded questions about one or more documents.

get_usage

Check plan quota before batch operations.

Example agent flow

"Check whether ~/actalumen-inbox/acme-msa.pdf meets our SOC2 vendor requirements and summarize the gaps."

The agent will:

  1. list_templates → find the SOC2 template.

  2. upload_document → get a document ID, wait for READY via get_document.

  3. start_verification → get a jobId.

  4. get_verification (polling) → receive the full report.

  5. Summarize the failed criteria back to you with page citations.

Verify your install

ACTALUMEN_API_KEY=ak_live_... npx -y @actalumen/mcp-server --health
# → ok — https://api.actalumen.com — org Acme Inc — upload dir /Users/.../actalumen-inbox

License

MIT

Available Tools

8 tools
chat_with_documentA

Ask a grounded question about one or more documents. Returns an answer with citations into the document. PII in source documents has already been redacted server-side, so answers cannot leak redacted data.

Inputs: documentIds (required), message (required), sessionId.

get_documentA

Get a document's status and metadata. Use this to poll after upload — call start_verification or chat_with_document only when status is READY. Status values: PROCESSING (embeddings running), READY (queryable), FAILED.

Inputs: documentId (required).

get_usageA

Check the organization's current plan, quota, and remaining allowance for documents, verifications, chat messages, and generated media. Call before kicking off expensive batch operations.

Inputs: no named parameters.

get_verificationA

Fetch verification job status and (when complete) the full report with per-criterion findings, citations, and pass/fail summary. Poll roughly every 5–10s after start_verification.

Inputs: jobId (required).

list_documentsA

List documents in the organization. Use this to find an existing document ID by name instead of re-uploading.

Inputs: limit, offset.

list_templatesA

List compliance criteria templates available to the organization (e.g., 'SOC2 Vendor', 'GDPR DPA'). Call this before start_verification to find the right templateId. Each template encodes a checklist of criteria a document is verified against.

Inputs: no named parameters.

start_verificationA

Run compliance verification on a document against a template (or ad-hoc criteria). Returns a jobId; the job runs async — poll get_verification until status is 'completed'. Requires the API key to have the 'verify' scope.

Inputs: documentId (required), templateId, criteria.

upload_documentA

Upload a PDF to ActaLumen for compliance verification. The server applies organization-configured PII redaction before storage — the agent will only ever see redacted content in subsequent calls. Returns a document ID; the document is PROCESSING until embeddings finish (poll get_document for status=READY).

Inputs: path (required), id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Upload, list, get status, verify, chat, check usage, list templates, and get verification results are all unique operations with no overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., upload_document, get_document, list_documents, start_verification). No mixing of conventions or inconsistent verb styles.

    Tool Count5/5

    8 tools is well-scoped for a document compliance verification service. Each tool earns its place, covering the essential operations without unnecessary bloat or missing critical steps.

    Completeness4/5

    The tool set covers the full lifecycle: upload, list, get status, verify, poll verification, chat with document, check usage, and list templates. Minor gaps like a delete or cancel operation exist, but the core workflow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to scan, redact, and govern sensitive data before sending it to external tools through DLP, secure chat, and shadow AI discovery tools.
      AGPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Redacts PII from LLM traces and tool payloads before they leave review, enabling PII scanning, payload redaction, sensitive field classification, privacy receipts, and trace audit exports.
      -