kratos

Kratos MCP provides an ultra-lean memory system that helps AI tools remember project context across sessions. It offers a compact set of 12 tools focused on memory management, security, project management, and system status, all designed to minimize context overhead while preserving important knowledge about your codebase, projects, and decisions. To use Kratos, you typically run it as an MCP server (via npx kratos-mcp or a global installation) and then configure your preferred AI tool (Claude, Cursor, Windsurf, Continue, or any MCP-compatible client) to connect to the server. Once configured, you can save memories, search them semantically, retrieve specific memories, and perform lightweight project management tasks—all while keeping data local in per-project SQLite databases. The Quick Start section in the README shows common setup patterns for Claude Desktop, Claude Code, and Cursor to integrate Kratos into your workflow. Kratos emphasizes zero configuration and auto-detection of relevant projects, with secure, private storage on your machine.

Prerequisites:

• Node.js and npm (or npx available via npm).
• Basic familiarity with MCP (Model Context Protocol) tooling and your AI integration.

Installation steps:

1. Install Kratos MCP globally (optional):

npm install -g kratos-mcp

2. Run Kratos MCP directly with npx (no installation required):

npx kratos-mcp

3. Or install as a project dependency in your app/repo:

npm install kratos-mcp

4. If you need to customize the server quickly, use the recommended npx invocation shown in the README configurations:

npx --yes kratos-mcp@latest

5. Ensure your AI tool is configured to point at the Kratos MCP server using the mcp_config example provided in the README (or through your tool’s MCP settings).

Tips and notes:

• Kratos stores data locally per project in a SQLite database, ensuring isolation between projects.
• The default storage location is ~/.kratos/ with a projects/ subfolder containing individual memories.db files.
• Kratos auto-detects your project based on git, package.json, or directory structure, reducing setup time.
• If you need to relocate data, Kratos supports changing the storage path (as noted in the README v1.6.1 update).
• The MCP configuration typically uses npx kratos-mcp@latest as the command, which keeps you aligned with the latest features and security fixes.
• When integrating with tools like Claude Desktop, Claude Code, or Cursor, you can copy-paste the provided mcpServers snippet into your tool’s config to enable seamless memory-backed interactions.
• If you encounter issues, verify that your environment has the required Node/NPX tooling and that the MCP server is reachable from your AI tool (network and firewall settings permitting).