English Français العربية

io.github.VelixarAi/memory

Official registry Search and web

Persistent memory for AI assistants. Store, search, and recall across sessions.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package velixar-mcp-server
Claude Code 
claude mcp add memory -e 'VELIXAR_API_KEY=<your velixar_api_key>' -- npx -y velixar-mcp-server@0.2.4
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "memory": {
            "command": "npx",
            "args": [
                "-y",
                "velixar-mcp-server@0.2.4"
            ],
            "env": {
                "VELIXAR_API_KEY": "<your velixar_api_key>"
            }
        }
    }
}

Environment variables

  • VELIXAR_API_KEY required secret Your Velixar API key (get one free at velixarai.com)

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Velixar MCP Server
  2. Why This Exists
  3. Quick Start
  4. Tool Surface
  5. Live Resources
  6. Workflow Prompts
  7. Workspace Isolation
  8. Host Compatibility
  9. Environment Variables
  10. Reliability
  11. SDKs
  12. CI/CD Integration
  13. License

Velixar MCP Server

The first cognitive memory server for AI assistants. Not a vector database wrapper — a full reasoning layer that gives your AI persistent memory, a knowledge graph, identity awareness, contradiction detection, and belief tracking across every session.

Works with any Model Context Protocol client: Claude Desktop, Kiro, Cursor, Windsurf, Continue.dev, or custom hosts.

Why This Exists

Every AI assistant starts from zero every conversation. Velixar fixes that — but not by just storing and retrieving text. The MCP server gives your assistant the ability to:

  • Orient itself in a workspace with a single call — no manual context assembly
  • Track how beliefs evolve over time and surface when they contradict
  • Build and traverse a knowledge graph of entities and relationships it discovers
  • Maintain a persistent identity model of who you are, what you prefer, and how you work
  • Distill sessions into durable memories automatically, with deduplication
  • Import and export your entire memory corpus for backup or migration

40 tools. 5 live resources. 19 workflow prompts. One npm install.

Quick Start

npm install -g velixar-mcp-server

Get an API key at velixarai.com/settings/api-keys, then add to your MCP client:

{
  "mcpServers": {
    "velixar": {
      "command": "velixar-mcp-server",
      "env": {
        "VELIXAR_API_KEY": "vlx_your_key_here"
      }
    }
  }
}

Restart your assistant. Done.

Tool Surface

Memory
ToolWhat it does
velixar_storeStore a memory with tags, tier, and type
velixar_searchSemantic search across all memories
velixar_listBrowse with pagination and filtering
velixar_updateEdit content or tags on an existing memory
velixar_deleteRemove a memory
Cognitive
ToolWhat it does
velixar_contextSynthesized workspace briefing — orientation in one call
velixar_identityGet, store, or update the user's profile, preferences, and expertise
velixar_contradictionsSurface conflicting facts or beliefs with resolution guidance
velixar_timelineHow a topic or belief evolved over time
velixar_patternsRecurring problem/solution motifs across your history
velixar_inspectDeep inspection of a specific memory with full provenance chain
velixar_graph_traverseWalk entity relationships — "what connects to X?"
velixar_distillExtract durable memories from session content with deduplication
Lifecycle
ToolWhat it does
velixar_session_saveSave a session summary for later recall
velixar_session_recallRestore context from a previous session
velixar_batch_storeStore up to 20 memories in one call
velixar_batch_searchRun up to 10 search queries simultaneously
velixar_consolidateMerge related memories into a single durable memory
velixar_retagBulk update tags across memories
velixar_exportExport memories as JSON or Markdown, optionally with graph data
velixar_importBulk import from JSON, Markdown, Notion, or Obsidian exports
System
ToolWhat it does
velixar_healthBackend connectivity, latency, workspace status
velixar_debugCache state, circuit breaker, API timings
velixar_capabilitiesFeature list, tool inventory, resource URIs
velixar_securityGet or set content scanning mode

Live Resources

Resources are injected into your assistant's context automatically — no tool call needed.

ResourceWhat it provides
velixar://system/constitutionBehavioral rules and cognitive modes for the assistant
velixar://identity/currentYour persistent user profile
velixar://memories/recentMost recent memories (compact)
velixar://memories/relevantContextually relevant memories based on current activity
velixar://domains/{domain}/shadow_graphKnowledge graph view for a specific domain

Workflow Prompts

16 built-in prompts that guide multi-step reasoning workflows:

  • Orientation — recall prior reasoning, build project context, profile an entity, orient-then-narrow
  • Conflict — resolve contradictions, identify knowledge gaps
  • Continuity — trace belief evolution, resume sessions, reconstruct decision paths
  • Lifecycle — distill sessions, consolidate topic memory, retag recent memories
  • Identity — summarize user identity, detect preference shifts, align response style
  • Enterprise — evaluate enterprise fit for a domain

Workspace Isolation

Memories are scoped to workspaces. Your personal project never bleeds into work.

PrioritySourceHow
1VELIXAR_WORKSPACE_ID env varExplicit
2.velixar.json in project root{ "workspace_id": "my-project" }
3Git root directory nameAutomatic

Host Compatibility

HostToolsResourcesPrompts
Kiro CLI✅✅✅
Claude Desktop✅✅✅
Cursor✅⚠️—
Windsurf✅⚠️—
Continue.dev✅✅✅

When a host doesn't support resources or prompts, the server degrades gracefully — all tools still work independently.

Environment Variables

VariableRequiredDescription
VELIXAR_API_KEYYesYour API key (starts with vlx_)
VELIXAR_WORKSPACE_IDNoExplicit workspace scope
VELIXAR_API_URLNoCustom API endpoint
VELIXAR_USER_IDNoExplicit end-user identity. Leave unset (recommended): the API derives scope from your key — you see your own memories, same as the dashboard. Set it only when one key serves multiple named end users
VELIXAR_DEBUGNotrue for verbose logging
VELIXAR_LOG_FORMATNojson for structured Datadog/CloudWatch logging
VELIXAR_HEALTH_PORTNoPort for HTTP health check endpoint

Reliability

  • Automatic retry with exponential backoff (3 attempts)
  • Circuit breaker — opens after sustained failures, auto-recovers
  • Cache fallback — serves stale data during outages rather than failing
  • Structured logging compatible with Datadog and CloudWatch

SDKs

Use Velixar directly from code:

  • JavaScript/TypeScript: npm install velixar — docs
  • Python: pip install velixar — docs

CI/CD Integration

License

MIT

Frequently asked questions

What is io.github.VelixarAi/memory?

Persistent memory for AI assistants. Store, search, and recall across sessions.

How do I install io.github.VelixarAi/memory?

It runs on your machine. In Claude Code: claude mcp add memory -e 'VELIXAR_API_KEY=<your velixar_api_key>' -- npx -y velixar-mcp-server@0.2.4. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.VelixarAi/memory need an API key?

Yes. It expects VELIXAR_API_KEY, which you set in its configuration.

Is io.github.VelixarAi/memory open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.VelixarAi/memory?

It is published by VelixarAi. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.