Velixar MCP Server

MCP server for Velixar persistent cognitive context — memory, identity, graph, time, and contradiction for LLMs. Exposed over MCP by the velixar mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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.

• 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

Adding it to your client

The server ships on npm as velixar-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• 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
• Webhook — POST /webhook/ci — generic CI event ingestion
• velixar_store — Store a memory with tags, tier, and type
• velixar_search — Semantic search across all memories
• velixar_list — Browse with pagination and filtering
• velixar_update — Edit content or tags on an existing memory
• velixar_delete — Remove a memory

Configuration

You will need 4 environment variables: VELIXAR_API_KEY, VELIXAR_WORKSPACE_ID, VELIXAR_API_URL, VELIXAR_USER_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Velixar.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the velixar mcp server does with a few real requests.

When to reach for it

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Velixar's toolset — Orientation, Conflict, Continuity and 11 more — is a fair guide to whether it matches your workflow. It is maintained by velixarai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.