Minime

Created By
manujbawa7 months ago
Universal infinite memory layer for Developer AI assistants. One shared brain across Claude, Cursor, Windsurf & more. 100% local, built on MCP standard. Stop re-explaining context
Overview

What is Minime?

Minime is a universal infinite memory layer designed for Developer AI assistants, enabling a shared memory system across various tools like Claude, Cursor, and Windsurf. It aims to eliminate the problem of AI forgetting context and decisions made in previous interactions.

How to use Minime?

To use Minime, start the server using Docker, integrate it with your preferred IDE, and begin coding with persistent memory that remembers your patterns and decisions.

Key features of Minime?

  • One connected memory system across multiple IDEs.
  • Cross-project intelligence that applies lessons learned automatically.
  • Document knowledge base for instant understanding of your system.
  • Smart project linking to connect related projects.
  • Zero-config memory that auto-tags and learns from interactions.
  • Privacy-first architecture that runs locally.

Use cases of Minime?

  1. Building authentication flows using previously established patterns.
  2. Generating code based on past decisions and debugging insights.
  3. Managing tasks with context from previous sessions.

FAQ from Minime?

  • Can Minime work with all IDEs?

Yes! Minime supports various IDEs including VS Code, Claude, and JetBrains.

  • Is my data safe with Minime?

Yes! Minime runs locally, ensuring your data never leaves your machine.

  • How does Minime remember my decisions?

Minime uses a persistent memory layer that connects your past interactions and decisions for future reference.

Server Config

{
  "mcpServers": {
    "minime-mcp": {
      "url": "http://localhost:8000/mcp"
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
manujbawa
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

2 hours 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