MCP Klaudium

Created By
MilosBastajaa year ago
Enhanced MCP memory system with dynamic compression, context management and thinking process integration. Based on the original MCP memory server.
Overview

what is MCP Klaudium?

MCP Klaudium is an enhanced memory server that integrates dynamic compression, context management, and thinking process capabilities, building upon the original MCP memory server.

how to use MCP Klaudium?

To use MCP Klaudium, follow the installation instructions provided in the repository (coming soon). Users can interact with the memory server through its API once set up.

key features of MCP Klaudium?

  • Basic knowledge graph functionality with CRUD operations and search capabilities.
  • Enhanced memory management with temporal awareness and importance tracking.
  • Categorization system for better organization of memory.
  • Memory statistics to monitor entities, relations, and memory size.

use cases of MCP Klaudium?

  1. Managing complex data relationships in research projects.
  2. Implementing advanced memory systems in AI applications.
  3. Analyzing temporal data for insights in various fields.

FAQ from MCP Klaudium?

  • What is the current status of MCP Klaudium?

The project is under active development with features being added incrementally.

  • How can I contribute to MCP Klaudium?

Contributions are welcome! You can submit a Pull Request on the GitHub repository.

  • Is there documentation available?

Documentation is being developed and will be available soon.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MilosBastaja
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago