Gmem MCP server
io.github.yksanjo/gmem·v1.1.0·1 starsPersistent, Solana-aware project memory for AI coding agents. Typed entities + git-aware diffs.
1 stars
Reviews
Write oneNobody has reviewed Gmem yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gmem tools (7, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
gmem.diffShow how memory state changed between two points in time. Accepts ISO 8601 timestamps OR git commit refs (HEAD, HEAD~3, branch names, full or short SHAs) — refs are resolved via `git show -s --format=%cI` in the active project root. v0.5 milestone.
gmem.ingest_anchorAuto-ingest an Anchor workspace: parses `Anchor.toml`, captures the IDL SHA-256 for each program from `target/idl/<name>.json`, and records the current git HEAD as the source commit. Writes one Program entity per (program, cluster) pair. v0.3 milestone.
gmem.ingest_hardhatAuto-ingest a Hardhat (EVM) workspace: walks up to the nearest hardhat.config.{ts,js,cjs,mjs}, reads every deployment artifact under deployments/<network>/<Contract>.json (hardhat-deploy convention), classifies the network into a canonical chain id, computes a stable ABI sha256, records git HEAD as sourceCommit. Writes one Contract entity per (chain, address). v1.1 milestone. Companion to gmem.ing
gmem.list_decisionsList all Decision entries for the active project, newest first.
gmem.recallRetrieve memory entries relevant to a natural-language query for the active Solana project. Ranked by BM25 over entity fields with a recency boost.
gmem.solana_contextRead the active Solana CLI context (`~/.config/solana/cli/config.yml`) and return the configured cluster, RPC URL, and the public address of the active keypair. Used to auto-attribute Decision writes to a developer wallet. v0.4 milestone. Does not return the secret key.
gmem.writewrite actionPersist a typed memory entry (Program / Account / Instruction / Decision / Finding / Integration). Append-only: re-writing the same logical entity creates a new version, never overwrites.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan22 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 80 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Gmem compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 1,119 Developer tools servers
- Tools
- 7
- the typical Developer tools server has 7
- Tools that change things
- 14%
- typical: 5%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 50% of 855 Developer tools servers
What its tools let an agent do: 6 read · 1 create
Install Gmem in Claude Code, Cursor or VS Code
Runs npx -y @yksanjo/gmem on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add gmem -- npx -y @yksanjo/gmem
What the publisher says
From the Gmem repository's README, as published. We do not edit it. Read it on GitHub
gmem
Persistent project memory for Solana AI agents.
A Model Context Protocol (MCP) server that gives AI coding agents — Claude Code, Cursor, or anything that speaks MCP — durable, Solana-aware memory of a project across sessions: program IDs, IDLs, PDA seeds, deployment state, architectural decisions, audit findings. So agents stop forgetting what they built yesterday.
Status: v1.1 — stable, with EVM support. Seven MCP tools, real implementations (no stubs), backward-compatible wire format:
Anchor.toml / workspace Cargo.toml, override with GMEM_DB)
- Storage: SQLite via better-sqlite3, one db file per project (auto-resolved from
reads return the latest; full history available via the in-process Store API
- Ranking: SQLite FTS5 BM25 with a recency boost
- Versioning: append-only — every write inserts a new (kind, natural_id, version) row;
records git HEAD as sourceCommit per Program
- Anchor ingest: gmem.ingest_anchor parses Anchor.toml, captures IDL sha256s,
classifies the cluster, derives the active keypair's pubkey (secret never leaks). gmem.write on a Decision auto-attributes author + authorCluster
- Solana CLI context: gmem.solana_context reads ~/.config/solana/cli/config.yml,
branch names, full and short SHAs)
- Git-aware diff: gmem.diff accepts both ISO timestamps and git refs (HEAD, HEAD~3,
classifies networks into canonical chain ids (base-mainnet 8453, optimism-mainnet 10, polygon-mainnet 137, arbitrum-one 42161, ethereum-mainnet 1, plus testnets), captures a reorder-invariant ABI SHA-256. New Contract entity kind for EVM smart contracts.
- EVM support (v1.1): gmem.ingest_hardhat parses Hardhat / hardhat-deploy workspaces,
- License: MIT
- Spec: see SPEC.md
- Entity schemas: see schema/
Why
Solana has moved decisively toward an agent-first developer experience. The Foundation's awesome-solana-ai repo indexes a strong layer of stateless reference skills — solana-dev-skill, magicblock-dev-skill, metaplex-skill, helius-phantom-skill, solana-game-skill, and more — that teach agents how to do things. The Solana Developer MCP exposes documentation. What's missing is the layer above: persistent project memory.
Today every Claude Code session on a Solana project starts cold. The agent doesn't remember the program ID it deployed yesterday, the PDA seeds it chose two weeks ago, the audit finding from last sprint, or why a specific Jupiter integration was rejected. The developer compensates by pasting context, hand-maintaining NOTES files, or re-explaining the project every session. That is a tax on every agent-assisted Solana developer.
gmem fixes this by being opinionated about Solana primitives — programs, accounts, instructions, PDAs, IDLs, cluster state, Anchor configs — rather than being a generic key-value store. It complements every existing skill in awesome-solana-ai rather than competing with any of them.
Install
npm install -g @yksanjo/gmemOr, to run it without a global install:
npx @yksanjo/gmemThe installed binary is still called gmem.
Or, to hack on the source:
git clone https://github.com/yksanjo/gmem.git ~/gmem
cd ~/gmem && npm install && npm run buildThen point your MCP client at it. For Claude Code:
// ~/.claude/mcp_servers.json
{
"mcpServers": {
"gmem": {
"command": "node",
"args": ["/absolute/path/to/gmem/dist/index.js"],
"env": { "GMEM_DB": "~/.gmem/memory.db" }
}
}
}Tools exposed (v0.1)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Gmem: common questions
- Is Gmem MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Gmem safety report
- How do I install Gmem?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Gmem need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Gmem maintained?
- The last commit was 118 days ago (2026-07-09). The latest release is v1.1.0.
- What can I use instead of Gmem?
- Servers from other publishers that do the same job: Palinode MCP server, Kindex MCP server and Kindex MCP server.
- How does Gmem compare with other Developer tools MCP servers?
- safety score 88/100 (higher than 75% of 1,119 Developer tools servers); tools 7 (the typical Developer tools server has 7); tools that change things 14% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Gmem
Same job from other publishers: the closest match first, then the best rated.
- PalinodeInspectable, correctable project memory in git-versioned Markdown for AI agents.not reviewedEstablishedC
- KindexPersistent knowledge graph and MCP server for AI workflows with git-tracked project context.not reviewedEstablishedA
- KindexPersistent knowledge graph and MCP server for AI workflows with git-tracked project context.not reviewedEstablishedB
- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
- Agent MemoryGit-native project memory for AI coding agents: Markdown source of truth, reviewable, secret-safe.not reviewedGrowingA