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
Hellogrowthcrm

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

a day ago
Payai X402 Tools

11 hours ago