Labsco
VelixarAi logo

velixar-mcp-server

β˜… 1

from VelixarAi

Persistant AI Memory

πŸ”₯πŸ”₯πŸ”₯βœ“ VerifiedAccount requiredNeeds API keys

Velixar MCP Server

npm License

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

25 tools. 5 live resources. 16 workflow prompts. One npm install.

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_IDNoUser ID for memory scoping
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

  • GitHub Actions: velixar-memory-sync β€” distill PR merges into memories
  • GitHub Actions: velixar-decision-capture β€” store issue resolutions as decisions
  • Webhook: POST /webhook/ci β€” generic CI event ingestion

License

MIT