Storing and searching text is table stakes. What earns its keep here is velixar_contradictions putting two of your own statements side by side with a severity, and velixar_coverage_check telling the assistant its retrieved memories do not actually cover the question — before it answers anyway.
A hosted memory layer reached over MCP. It stores memories scoped to a workspace, searches them semantically, builds a knowledge graph of the entities it finds, tracks how a belief changed over time, and flags statements that cannot both be true.
- Memory basics — velixar_store, velixar_search, velixar_list, velixar_update, velixar_delete, velixar_batch_store
- Orientation — velixar_context synthesises a working brief for the workspace; velixar_prepare_context assembles a token-budgeted package and velixar_refine_context fills a gap in it
- Knowledge graph — velixar_graph_traverse, velixar_graph_search, velixar_graph_stats, and velixar_lineage for what a memory was reasoned from
- Conflict and change — velixar_contradictions, velixar_timeline, velixar_patterns
- Sessions — velixar_session_save, velixar_session_recall, velixar_session_resume, and velixar_distill to pull durable memories out of session content
- Curation — velixar_consolidate, velixar_retag, velixar_export, velixar_import, and velixar_upload for PDF, Markdown, text, CSV, JSON, DOCX and code files
- Live data — velixar_list_sources, velixar_query_source, velixar_discover_data
- Guardrails and operations — velixar_coverage_check, velixar_security, velixar_health, velixar_debug, velixar_audit_log, velixar_capabilities, velixar_identity, velixar_inspect, velixar_multi_search, velixar_search_neighborhood
The npm package velixar-mcp-server over stdio, with VELIXAR_API_KEY in the environment. Memories are scoped to a workspace resolved in order from VELIXAR_WORKSPACE_ID, then a .velixar.json file in the project root, then the git root directory name. VELIXAR_API_URL points at a different endpoint, VELIXAR_USER_ID is only needed when one key serves several named end users, and VELIXAR_DEBUG, VELIXAR_LOG_FORMAT and VELIXAR_HEALTH_PORT cover logging and health checks.
One command plus a key — npm install -g velixar-mcp-server, then supply credentials