Kratos MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_saveC | Save a memory document to the active project |
| memory_searchC | Search memory documents in the active project |
| memory_get_recentB | Get recent memories from active project |
| memory_getB | Get a specific memory by ID with full text |
| memory_get_multipleB | Get multiple memories by IDs with full text (bulk operation) |
| memory_askC | Ask questions about your memories using natural language |
| memory_forgetB | Delete a memory by ID |
| security_scanB | Scan text for PII and secrets |
| project_switchC | Switch to a different project |
| project_currentA | Get current active project |
| change_storage_pathB | Dynamically change where Kratos stores data (with automatic migration) |
| system_statusA | Get system status and statistics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| System Status | Current system status and statistics |
TDQS
Scored across 12 tools
Most tools have distinct purposes, but memory_get and memory_get_multiple are closely related, and memory_ask could be conflated with memory_search if not careful. Overall, boundaries are clear.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to navigate.
With 12 tools, the set is well-scoped for a memory and project management system, neither too sparse nor overwhelming.
Missing a memory update tool and project listing capability. The set covers core CRUD for memories but lacks lifecycle operations for projects and explicit memory updates.