xgmem MCP Memory Server

Created By
meetdhanani17a year ago
Global MCP server that manage all the project data,
Overview

what is xgmem?

xgmem is a TypeScript-based Model Context Protocol (MCP) server designed to manage project-specific and knowledge graph-based memory for Claude, LLM agents, and other tools. It enables the storage, retrieval, and management of entities, relations, and observations per project, focusing on flexibility and cross-project knowledge sharing.

how to use xgmem?

To use xgmem, you need to configure it in your MCP setup, install dependencies, build the project, and run it either in development or production mode. You can also use Docker for deployment.

key features of xgmem?

  • Knowledge graph storage for entities, relations, and observations
  • CRUD operations via MCP tools
  • Persistence to disk (memory.json)
  • Docker and TypeScript support

use cases of xgmem?

  1. Agents and LLMs that require structured memory storage and retrieval per project.
  2. Cross-project knowledge sharing and migration.
  3. Scalable, disk-persistent, and queryable memory for agent ecosystems.

FAQ from xgmem?

  • What is the purpose of xgmem?

xgmem serves as a memory server for managing project-specific data and facilitating knowledge sharing across projects.

  • How do I install xgmem?

You can install xgmem by running npm install after adding it to your MCP configuration.

  • Can I run xgmem in Docker?

Yes! xgmem can be built and run using Docker for easier deployment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
meetdhanani17
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Voyei

3 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.

13 hours ago