Kova Mind MCP Server
OfficialThe Kova Mind MCP Server provides AI memory management and zero-exposure credential vault capabilities for MCP-compatible clients (Claude Desktop, Cursor, Windsurf, VS Code, etc.).
Memory Tools:
memory_extract: Parse conversation messages and store learned patterns about a user.memory_recall: Retrieve relevant memories for a given context, with configurable confidence thresholds.memory_reinforce: Confirm, deny, strengthen, or weaken stored memory patterns based on feedback.memory_surprise: Score how novel or contradictory new content is compared to existing memories.memory_health: Check the health status of the Kova Mind API.
Vault Tools (Zero-Exposure Credentials):
vault_setup: Initialize the secrets vault; returns 12 recovery words for safekeeping.vault_unlock/vault_lock: Unlock the vault with a passphrase, or lock it and zero the encryption key from memory.vault_store: Securely store credentials (API keys, passwords, SSH keys, OAuth tokens, etc.), returning an opaque handle — actual values are never exposed to the AI.vault_handles: List all credential handles (labels and types only, not values).vault_find: Search for credentials using a natural-language query, returning matching handles with relevance scores.vault_execute: Perform HTTP requests or browser form fills using a stored credential handle — credentials flow through a secure side channel and are never exposed to the AI.
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., "@Kova Mind MCP Serverrecall memories about my recent projects"
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.
@kovamind/mcp-server
MCP server for Kova Mind — use AI memory in Claude Desktop, Cursor, Windsurf, VS Code, and any MCP-compatible client.
Quick setup
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"kovamind": {
"command": "npx",
"args": ["-y", "@kovamind/mcp-server"],
"env": {
"KOVAMIND_API_KEY": "km_live_xxx",
"KOVAMIND_USER_ID": "my-user"
}
}
}
}Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"kovamind": {
"command": "npx",
"args": ["-y", "@kovamind/mcp-server"],
"env": {
"KOVAMIND_API_KEY": "km_live_xxx",
"KOVAMIND_USER_ID": "my-user"
}
}
}
}VS Code
Add to .vscode/mcp.json:
{
"servers": {
"kovamind": {
"command": "npx",
"args": ["-y", "@kovamind/mcp-server"],
"env": {
"KOVAMIND_API_KEY": "km_live_xxx",
"KOVAMIND_USER_ID": "my-user"
}
}
}
}Windsurf
Add to your Windsurf MCP config:
{
"mcpServers": {
"kovamind": {
"command": "npx",
"args": ["-y", "@kovamind/mcp-server"],
"env": {
"KOVAMIND_API_KEY": "km_live_xxx",
"KOVAMIND_USER_ID": "my-user"
}
}
}
}Related MCP server: CacheTank MCP Server
Environment variables
Variable | Required | Default | Description |
| Yes | — | Your Kova Mind API key |
| No |
| API base URL |
| No | — | Default user ID for all operations |
Available tools
Memory
Tool | Description |
| Extract memory patterns from a conversation |
| Retrieve relevant memories for a context |
| Confirm, deny, strengthen, or weaken a pattern |
| Score how novel content is vs existing memory |
| Check API health status |
Vault (zero-exposure credentials)
Credential values never reach the AI. Store a credential once, get back an opaque handle, then ask the AI to act with that handle — the value flows through a secure side channel.
Tool | Description |
| One-time vault setup. Returns 12 recovery words — store them safely |
| Unlock the vault with your passphrase |
| Lock the vault and zero the key from memory |
| Store a credential. Returns an opaque handle |
| List available handles (never the values) |
| Search handles by natural-language query |
| Run an action (http request, browser fill) using a handle |
Troubleshooting
403 — API key is bound to a different agent identity
A Kova Mind API key can be bound server-side to a single user_id (agent identity). If a request's user_id does not match the identity the key is bound to, the API returns:
HTTP 403 {"detail":"API key is bound to a different agent identity"}This surfaces in any tool that takes a user_id (e.g. memory_extract, memory_recall, memory_surprise) as a ... failed: API error 403: ... message.
What to do:
Make sure the
user_idyou pass (or theKOVAMIND_USER_IDenv var) matches the identity the key was issued for.Unbound keys are unaffected — they pass the client-supplied
user_idthrough unchanged, so a single unbound key can serve multiple users.If you need one key per agent, bind the key to that agent's
user_idand always send the matchinguser_id.
Get an API key
Sign up at kovamind.io to get your API key.
License
MIT
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/KovaMind/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server