CC-MCP

Created By
Beginnersguide13810 months ago
🌟 Revolutionary AI Context Management: Solving LLM Memory Loss in Long Conversations Long-term conversational consistency management system for LLM-powered AI agents 🚀 The Problem We Solve Traditional LLMs suffer from "intent forgetting" in long conversations: ❌ Lose track of the original goal after a few turns ❌ Forget important constraints and decisions ❌ Provide inconsistent responses across dialogue sessions ❌ Require users to constantly remind the AI of context CC-MCP provides intelligent context management tools to help MCP clients maintain consistency. 🎯 Real-World Impact Before CC-MCP: User: "I want to build an AI assistant app" AI: "Sure! Here are some general approaches..." [10 messages later] User: "Remember, budget is 500K yen, 3 months timeline" AI: "What project are we talking about?" ❌ After CC-MCP: User: "I want to build an AI assistant app" AI: "Great! Let me help you design this system..." [10 messages later] User: "What about deployment options?" AI: "For your AI assistant app (budget: 500K yen, 3-month timeline, security priority), here are deployment strategies that fit your constraints..." ✅

Server Config

{
  "mcpServers": {
    "cc-mcp": {
      "autoApprove": [
        "process_user_message",
        "start_session",
        "get_debug_info",
        "list_sessions",
        "get_session_stats",
        "export_context",
        "import_context",
        "clear_context",
        "end_session"
      ],
      "disabled": false,
      "timeout": 120,
      "type": "stdio",
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/path/to/your/cc-mcp",
        "main.py"
      ],
      "env": {
        "CLASSIFIER_API_URL": "https://api.openai.com/v1/chat/completions",
        "CLASSIFIER_API_KEY": "your_openai_api_key_here",
        "CLASSIFIER_MODEL": "gpt-4o-mini"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Beginnersguide138
Star
-
Language
-
License
-
Category

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