Kova Mind MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KOVAMIND_API_KEY | Yes | Your Kova Mind API key | |
| KOVAMIND_API_URL | No | API base URL | https://api.kovamind.io |
| KOVAMIND_USER_ID | No | Default user ID for all operations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_extractC | Extract memory patterns from a conversation. Parses messages and stores learned patterns about the user. |
| memory_recallB | Retrieve relevant memory patterns for a given context. Use this to recall what you know about a user. |
| memory_reinforceA | Reinforce or deny a stored memory pattern. Use 'confirmed' when the user validates a memory, 'denied' when they contradict it. |
| memory_surpriseA | Score how surprising/novel new content is compared to existing memories. High scores indicate contradictions with stored knowledge. |
| memory_healthA | Check if the Kova Mind API is healthy and responding. |
| vault_setupA | Set up the secrets vault for the first time. Returns 12 recovery words — store them safely. The vault stores credentials that agents can use without ever seeing the values. |
| vault_unlockA | Unlock the secrets vault with your passphrase. Required before storing or using credentials. |
| vault_lockA | Lock the secrets vault. Zeros the encryption key from memory. |
| vault_storeA | Store a new credential in the vault. Returns an opaque handle — you will never see the credential values. |
| vault_handlesA | List available credential handles. You will never see the credential values — only the handle, label, and type. |
| vault_findA | Find credentials matching a search query. Returns matching handles with relevance scores. You will never see credential values. |
| vault_executeB | Execute an action using a credential. The credential is never exposed to you — it flows through a secure side channel. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Tools are clearly grouped by domain (memory vs vault), and within each group, actions are distinct. However, memory_extract vs memory_recall could confuse agents about when to extract vs recall. Overall, most tools have well-defined boundaries.
All tool names follow a consistent verb_noun pattern with a domain prefix (memory_ or vault_). Snake_case is used uniformly, making the naming predictable and easy to navigate.
With 12 tools covering two distinct subsystems (memory and vault), the count is well-scoped. Each tool serves a clear purpose without unnecessary bloat or deficiency.
The memory subsystem covers extraction, recall, reinforcement, and novelty scoring but lacks explicit deletion or listing of all memories. The vault subsystem covers setup, unlock, store, find, handles, execute, and lock, but could benefit from a credential update or delete operation. Minor gaps exist but core workflows are covered.