Context Keeper

Created By
redleaves8 months ago
**Context Keeper** 基于LLM驱动的智能上下文记忆管理系统,专为AI Agent提供企业级记忆能力。 **核心创新**:独创"宽召回+精排序"架构,通过两阶段LLM协作实现多维度检索融合(向量+时间线+知识图谱),准确率从传统RAG的45%提升至**75%+**,召回率达**80%+**。 **技术亮点**:完整实现MCP协议(HTTP/WebSocket/SSE三种传输),四维统一上下文模型(Project/Topic/Conversation/Code),支持短期/长期记忆智能转换。 **性能表现**:10000+ QPS并发能力,P95延迟<500ms,用户/工作空间完全隔离。 **开源生态**:MIT许可,Go语言实现,深度集成Cursor/VSCode IDE。让AI助手真正拥有持续记忆能力,告别重复解释,开启智能协作新时代。
Overview

what is Context Keeper?

Context Keeper is an LLM-driven intelligent context memory management system designed to provide enterprise-level memory capabilities for AI agents. It addresses the common issues of AI assistants forgetting project backgrounds and repetitive queries.

how to use Context Keeper?

To use Context Keeper, integrate it with your AI assistant through the provided MCP protocol, and it will automatically manage context and memory during interactions.

key features of Context Keeper?

  • Unique "wide recall + precise ranking" architecture for improved accuracy and recall rates.
  • Supports multiple context types: Project, Topic, Conversation, and Code.
  • High performance with over 10,000 QPS and user isolation.
  • Deep integration with IDEs like Cursor and VSCode for automatic context tracking.

use cases of Context Keeper?

  1. Code review assistance by linking historical discussions.
  2. Onboarding new team members with quick access to project knowledge.
  3. Building a team knowledge base for continuous learning and memory retention.

FAQ from Context Keeper?

  • Can Context Keeper help with all types of AI assistants?

Yes! It is designed to enhance any AI assistant with persistent memory capabilities.

  • Is Context Keeper open source?

Yes! It is available under the MIT license on GitHub.

  • How does Context Keeper ensure data privacy?

It provides complete user and workspace isolation to protect sensitive information.

Project Info
Created At
8 months ago
Updated At
7 months ago
Author Name
redleaves
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago