MemGPT MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MemGPT MCP Server?

MemGPT MCP Server is a TypeScript-based server that implements a memory system for large language models (LLMs), allowing users to chat with various LLM providers while maintaining conversation history.

how to use MemGPT MCP Server?

To use MemGPT MCP Server, install the necessary dependencies, build the server, and configure it with your LLM provider's API keys. You can then interact with the server through its chat tools.

key features of MemGPT MCP Server?

  • Supports multiple LLM providers (OpenAI, Anthropic, OpenRouter, Ollama)
  • Tools for sending messages, retrieving conversation history, and clearing memory
  • Ability to switch between different models and providers
  • Unlimited memory retrieval option

use cases of MemGPT MCP Server?

  1. Engaging in conversations with LLMs while keeping track of context.
  2. Utilizing different models for specific tasks like customer support or content generation.
  3. Debugging and inspecting LLM interactions using the MCP Inspector.

FAQ from MemGPT MCP Server?

  • Can I use multiple LLM providers?

Yes! MemGPT MCP Server supports multiple providers including OpenAI and Anthropic.

  • How do I clear my conversation history?

You can use the clear_memory tool to remove all stored memories.

  • Is there a limit to how much conversation history I can retrieve?

No, you can retrieve unlimited conversation history by using the get_memory tool with the limit set to null.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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