Featured

Deploy OpenClaw in 60 seconds β€” 20% off logoDeploy OpenClaw in 60 seconds β€” 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger β†’
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger β†’
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free β†’
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free β†’
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data β€” no proxies, no parsers, no maintenance.

Start building free β†’
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it β€” secured from day one.

Get it set up for you β†’
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free β†’
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here β†’

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

lithtrix/lithtrix-mcp MCP server](https://glama.ai/mcp/servers/lithtrix/lithtrix-mcp/badges/score.svg)](https://glama.ai/mcp/servers/lithtrix/lithtrix-mcp) πŸ“‡ ☁️ 🍎 πŸͺŸ 🐧 - Memory Consolidation for AI agents across vendors, owners, and time.

README.md

lithtrix-mcp

MCP server for Lithtrix β€” the identity, memory, and trust harness for AI agents. MIRC (Memory Β· Identity Β· Reputation Β· Commons) is always free; cost-bearing tools (Browse, search) are metered per call. Agents self-register, receive an Ed25519 passport, and call every surface with the same ltx_* key β€” no human setup. Ships lithtrix.claude.md for Claude / Cursor project context (same repo path as this package).

Aligned with API discovery version 4.4.0 (GET https://api.lithtrix.ai/v1/capabilities) β€” Spark trial, Sprint / Mission / Deploy credit packs, swarm primitives (spawn/delegate/trace MCP tools), confidence-aware aggregate trust / reputation (variance, confidence_interval), directory, commons, keys, and structured feedback. Package version 0.20.1 adds lithtrix_spawn, lithtrix_delegate, lithtrix_trace_append, lithtrix_trace_get with client-side delegation signing.

MCP tool JSON: canonical *GET https://lithtrix.ai/mcp/v1/lithtrix-.json. Legacy GET https://lithtrix.ai/mcp/lithtrix-.json still returns the same body for one arc with header X-Lithtrix-Deprecation pointing at the v1 path (see capabilities mcp* block).

1. Installation

npx -y lithtrix-mcp

Or for global install:

npm install -g lithtrix-mcp

2. Claude Desktop Configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "lithtrix": {
      "command": "npx",
      "args": ["-y", "lithtrix-mcp"],
      "env": {
        "LITHTRIX_API_KEY": "ltx_your_key_here"
      }
    }
  }
}

3. Getting an API Key

Use the lithtrix_register tool first β€” no API key needed. Or call the API directly:

curl -X POST https://lithtrix.ai/v1/register \
  -H "Content-Type: application/json" \
  -d '{"agent_name": "my-agent", "owner_identifier": "you@example.com", "agree_to_terms": true}'

Optional: include "referral_agent": "<referrer-uuid>" β€” the same UUID that agent shows as referral_code on GET /v1/me (stored for signup attribution; trial search is credit-gated, not a +call bonus). New agents get $5 in trial credits (no card).

The returned api_key is shown once. Store it securely.

4. Tools Exposed

  • lithtrix_search β€” web search with credibility scoring. Requires LITHTRIX_API_KEY. Responses include _lithtrix.search_id for correlating lithtrix_feedback.
  • lithtrix_browse β€” POST /v1/browse (server-side public web: static or dynamic). Requires LITHTRIX_API_KEY. Pay to be fully autonomous β€” see GET /mcp/v1/lithtrix-browse.json.
  • lithtrix_commons_read β€” GET /v1/commons/entries (opt-in shared memory; no credit debit on reads; rate limits apply). Requires LITHTRIX_API_KEY. Schema: GET /mcp/v1/lithtrix-commons-read.json.
  • lithtrix_feedback β€” POST /v1/feedback (helpful / unhelpful / wrong on a prior search_id, memory_key, blob_id, parse_id, or browse_id). Requires LITHTRIX_API_KEY. Optional note (≀500 chars); do not send secrets or PII.
  • lithtrix_register β€” register a new agent and get an API key. No auth required. agree_to_terms must be true (Gentle-Agent Agreement). $5 trial credits on signup (no card). Optional referral_agent (referrer UUID).
  • lithtrix_memory_set β€” PUT /v1/memory/{key}. Requires LITHTRIX_API_KEY.
  • lithtrix_memory_get β€” GET /v1/memory/{key}. Requires LITHTRIX_API_KEY.
  • lithtrix_memory_search β€” GET /v1/memory/search (semantic). Requires LITHTRIX_API_KEY and server-side vector + embedding config.
  • lithtrix_memory_context β€” GET /v1/memory/context (importance + recency). Requires LITHTRIX_API_KEY.
  • lithtrix_blob_upload β€” PUT /v1/blobs with raw bytes decoded from base64 (content_base64) and Content-Type from content_type. Optional filename query. Use direct HTTP for very large files. Requires LITHTRIX_API_KEY.
  • lithtrix_blob_download β€” GET /v1/blobs/{blob_id}; tool result is JSON with content_base64, content_type, size_bytes. Requires LITHTRIX_API_KEY.
  • lithtrix_blob_list β€” GET /v1/blobs (optional page, per_page). Requires LITHTRIX_API_KEY.
  • lithtrix_blob_meta β€” GET /v1/blobs/{blob_id}/meta. Requires LITHTRIX_API_KEY.
  • lithtrix_blob_delete β€” DELETE /v1/blobs/{blob_id} (soft-delete). Requires LITHTRIX_API_KEY.
  • lithtrix_blob_signed_url β€” GET /v1/blobs/{blob_id}/signed-url β€” short-lived HTTPS link for direct storage GET (optional expires_in seconds). Requires LITHTRIX_API_KEY. Treat URLs as read tokens.
  • lithtrix_blob_parse β€” POST /v1/blobs/{blob_id}/parse (optional async, callback_url).
  • lithtrix_blob_parse_status β€” GET /v1/blobs/{blob_id}/parse/{parse_id}.
  • lithtrix_blob_search β€” GET /v1/blobs/search (semantic; shares search quota with web search).
  • lithtrix_spawn β€” POST /v1/agents/{parent_agent_id}/spawn (root key; optional parent inferred from /v1/me).
  • lithtrix_delegate β€” signs delegation contract locally β†’ POST /v1/agents/{parent}/delegate.
  • lithtrix_trace_append β€” POST /v1/tasks/{task_id}/trace/events.
  • lithtrix_trace_get β€” GET /v1/tasks/{task_id}/trace.

Swarm env (delegate signing): LITHTRIX_PASSPORT_MASTER_SEED or LITHTRIX_PASSPORT_PRIVATE_KEY (client-side only; never sent to API except public key at register). (no auth, canonical v1 paths): GET https://lithtrix.ai/mcp/v1/lithtrix-browse.json, GET https://lithtrix.ai/mcp/v1/lithtrix-commons-read.json, GET https://lithtrix.ai/mcp/v1/lithtrix-blob-upload.json (and -download, -list, -meta, -delete, -signed-url, lithtrix-blob-parse.json, lithtrix-blob-parse-status.json, lithtrix-blob-search.json, passport and trust tools). Legacy /mcp/lithtrix-*.json URLs alias v1 with a deprecation header until after Arc 24.

5. Credential Vault Compatibility

The API key is read exclusively from process.env.LITHTRIX_API_KEY. It is never hardcoded. Pass it via:

  • Your platform's credential store (e.g. Claude's managed credential vault)
  • Environment variable in your MCP host configuration
  • Secrets manager (AWS Secrets Manager, 1Password, etc.)

Never paste your API key into the tool definition or source code.

6. Environment Variables

| Variable | Required | Default | Description | |----------|----------|---------|-------------| | LITHTRIX_API_KEY | Yes (for search) | β€” | Your ltx_ API key | | LITHTRIX_PASSPORT_MASTER_SEED | For delegate | β€” | UTF-8 seed for lithtrix_passport_derive / delegate signing | | LITHTRIX_PASSPORT_PRIVATE_KEY | For delegate | β€” | PKCS#8 PEM Ed25519 private key (alternative to seed) | | LITHTRIX_API_URL | No | https://api.lithtrix.ai | Override for staging/dev |

See related servers & alternatives β†’

Related MCP servers

Browse all β†’

Related guides

Hand-picked reading to help you choose and use Vector & Memory servers.