1. Conduid
  2. Data
  3. indra_db_mcp
MCP server · Data

indra_db_mcp

MCP server for indra_db - a content-addressed graph database for versioned thoughts

Unclaimed data
39Low

Scored 3 months ago · breakdown

About indra_db_mcp

indra_db_mcp is an MCP server published by git+moonstripe in the Data category: mCP server for indra_db - a content-addressed graph database for versioned thoughts. It has been installed 0 times through Conduid.

Install

Install
npx indra_db_mcp
Claude Code
claude mcp add indra-db-mcp -- npx -y indra_db_mcp
npx
npx -y indra_db_mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about indra_db_mcp

Powered by Claude · Grounded in docs

I know everything about indra_db_mcp. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

indra_db_mcp

Persistent memory for AI reasoning and decisions.

An MCP server that gives AI agents memory that persists across sessions. Built on indra_db — a git-like database for versioned thoughts.

The Problem

AI agents start fresh every session. Yesterday's insights evaporate. Decisions get re-made. Reasoning chains vanish.

indra_db_mcp changes that by giving agents:

  • 🧠 Persistent memory — Record reasoning that survives session boundaries
  • 🔍 Semantic search — Find past decisions by meaning, not keywords
  • 🌿 Branching — Explore alternatives without losing the main thread
  • 📜 History — See how understanding evolved over time

Quick Start

Install

No installation required — use bunx for automatic updates:

bunx -y indra_db_mcp@latest

Or install globally:

bun add -g indra_db_mcp

Configure Your Agent

Claude Code — Add to your project's CLAUDE.md:

@import node_modules/indra_db_mcp/INDRA_INSTRUCTIONS.md

Claude Desktop — Add to claude_desktop_config.json:

{
  "mcpServers": {
    "indra": {
      "command": "bunx",
      "args": ["-y", "indra_db_mcp@latest"]
    }
  }
}

OpenCode — Add to ~/.config/opencode/opencode.json:

{
  "mcp": {
    "indra": {
      "command": ["bunx", "-y", "indra_db_mcp@latest"],
      "type": "local"
    }
  },
  "instructions": ["~/.config/opencode/instructions/indra.md"]
}

Then copy INDRA_INSTRUCTIONS.md:

mkdir -p ~/.config/opencode/instructions
curl -o ~/.config/opencode/instructions/indra.md \
  https://raw.githubusercontent.com/moonstripe/indra_db_mcp/main/INDRA_INSTRUCTIONS.md

Generic MCP Client:

{
  "mcpServers": {
    "indra": {
      "command": "bunx",
      "args": ["-y", "indra_db_mcp@latest"],
      "env": {
        "INDRA_DB_PATH": "./.indra"
      }
    }
  }
}

Tools

Tool Purpose
indra_remember Record reasoning, decisions, and insights
indra_search Find past reasoning by meaning (or "*" for all)
indra_status Check current branch and entry count
indra_branch Create, switch, or list branches
indra_experiment Quick sandbox for exploring alternatives
indra_history See how reasoning evolved
indra_diff Compare two points in history

Example Usage

An agent might use Indra like this:

User: Should I use PostgreSQL or MongoDB for my e-commerce app?

Agent thinking:
  → indra_search({ query: "database recommendations" })
  → Found: Previously recommended PostgreSQL for relational data with transactions
  
  → Making recommendation based on past reasoning + current context
  
  → indra_remember({ 
      content: "Recommended PostgreSQL for e-commerce app. User has relational product 
               catalog, needs transactions for orders. Consistent with past guidance.",
      id: "ecommerce-db-decision"
    })

Later:

User: Why did you recommend PostgreSQL?

Agent:
  → indra_search({ query: "ecommerce database" })
  → Found the reasoning from the previous session
  → Can explain the decision with full context

Branching for Exploration

Agent: Let me explore an alternative approach...

  → indra_experiment({ name: "try-nosql-approach" })
  
  [Explores MongoDB path, records reasoning]
  
  → indra_diff({ from: "main" })  // Compare with main reasoning
  
  → indra_branch({ action: "switch", name: "main" })  // Back to main

Environment Variables

Variable Description Default
INDRA_DB_PATH Path to database file ./.indra
INDRA_API_URL API for sync (optional) https://api.indradb.net

How It Works

  1. Content-addressed storage — Every entry is hashed. Identity comes from content.
  2. Local embeddings — Uses sentence-transformers/all-MiniLM-L6-v2 for semantic search.
  3. Git-like versioning — Commits create snapshots. Branches enable parallel exploration.
  4. Single file — Everything in one .indra file. Easy to backup and share.

Architecture

┌─────────────────────────────────────────────────────────┐
│                    MCP Client (Claude)                   │
└─────────────────────────┬───────────────────────────────┘
                          │ MCP Protocol (stdio)
┌─────────────────────────▼───────────────────────────────┐
│                   indra_db_mcp (Bun)                     │
│  ┌─────────────┐  ┌──────────────┐  ┌───────────────┐  │
│  │   MCP SDK   │  │ IndraClient  │  │ Auto-sync     │  │
│  └─────────────┘  └──────┬───────┘  └───────────────┘  │
└──────────────────────────┼──────────────────────────────┘
                           │ CLI subprocess (JSON)
┌──────────────────────────▼──────────────────────────────┐
│                    indra CLI (Rust)                      │
│  ┌─────────────┐  ┌──────────────┐  ┌───────────────┐  │
│  │ Graph Store │  │  Embeddings  │  │  Git-like VCS │  │
│  └─────────────┘  └──────────────┘  └───────────────┘  │
└─────────────────────────────────────────────────────────┘

Visualize on IndraDB

Push to IndraDB for 3D visualization and analytics:

indra login
indra remote add origin username/my-memory
indra push origin

License

MIT

Related

README mirrored from the source repository 3 months ago. The original is authoritative.

Questions

About indra_db_mcp

How do I install indra_db_mcp?

Run npx indra_db_mcp, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is indra_db_mcp safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is indra_db_mcp still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.