Velixar MCP Server
OfficialProvides structured logging integration with Datadog for monitoring and debugging.
Allows syncing memories and capturing decisions from GitHub Actions workflows.
Enables importing memories from Notion exports.
Enables importing memories from Obsidian exports.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Velixar MCP Serverget my current identity profile"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
25 tools. 5 live resources. 16 workflow prompts. One npm install.
Related MCP server: Recall
Quick Start
npm install -g velixar-mcp-serverGet 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
Tool | What it does |
| Store a memory with tags, tier, and type |
| Semantic search across all memories |
| Browse with pagination and filtering |
| Edit content or tags on an existing memory |
| Remove a memory |
Cognitive
Tool | What it does |
| Synthesized workspace briefing — orientation in one call |
| Get, store, or update the user's profile, preferences, and expertise |
| Surface conflicting facts or beliefs with resolution guidance |
| How a topic or belief evolved over time |
| Recurring problem/solution motifs across your history |
| Deep inspection of a specific memory with full provenance chain |
| Walk entity relationships — "what connects to X?" |
| Extract durable memories from session content with deduplication |
Lifecycle
Tool | What it does |
| Save a session summary for later recall |
| Restore context from a previous session |
| Store up to 20 memories in one call |
| Run up to 10 search queries simultaneously |
| Merge related memories into a single durable memory |
| Bulk update tags across memories |
| Export memories as JSON or Markdown, optionally with graph data |
| Bulk import from JSON, Markdown, Notion, or Obsidian exports |
System
Tool | What it does |
| Backend connectivity, latency, workspace status |
| Cache state, circuit breaker, API timings |
| Feature list, tool inventory, resource URIs |
| Get or set content scanning mode |
Live Resources
Resources are injected into your assistant's context automatically — no tool call needed.
Resource | What it provides |
| Behavioral rules and cognitive modes for the assistant |
| Your persistent user profile |
| Most recent memories (compact) |
| Contextually relevant memories based on current activity |
| Knowledge 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.
Priority | Source | How |
1 |
| Explicit |
2 |
|
|
3 | Git root directory name | Automatic |
Host Compatibility
Host | Tools | Resources | Prompts |
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
Variable | Required | Description |
| Yes | Your API key (starts with |
| No | Explicit workspace scope |
| No | Custom API endpoint |
| No | User ID for memory scoping |
| No |
|
| No |
|
| No | Port 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:
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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/VelixarAi/velixar-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server