optimized-memory-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is optimized-memory-mcp-server?

The optimized-memory-mcp-server is a project designed to test and demonstrate Claude AI's coding abilities, focusing on good AI workflows and prompt design. It implements a persistent memory system using a local knowledge graph, allowing Claude to remember user information across chats.

How to use optimized-memory-mcp-server?

To use the server, set it up with Docker or NPX, and configure it in your claude_desktop_config.json. You can then interact with the server to create entities, relations, and observations in the knowledge graph.

Key features of optimized-memory-mcp-server?

  • Persistent memory using a local knowledge graph
  • Ability to create and manage entities and their relationships
  • API for adding, deleting, and searching entities and observations
  • Integration with Claude AI for personalized interactions

Use cases of optimized-memory-mcp-server?

  1. Storing user preferences and behaviors for personalized AI interactions.
  2. Managing relationships between different entities in a knowledge graph.
  3. Enhancing AI's memory capabilities for better user experience.

FAQ from optimized-memory-mcp-server?

  • What programming language is used?

The server is implemented in Python.

  • Is there a license for this project?

Yes, it is licensed under the MIT License, allowing free use, modification, and distribution.

  • How can I build the server?

You can build it using Docker with the provided Dockerfile.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
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.

6 minutes ago