Install
$ agentstack add mcp-aristoapp-membase ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
[](https://cursor.com/en/install-mcp?name=membase&config=eyJ1cmwiOiJodHRwczovL21jcC5tZW1iYXNlLnNvL21jcCJ9) [](https://insiders.vscode.dev/redirect/mcp/install?name=membase&config=%7B%22type%22%3A%20%22http%22%2C%20%22url%22%3A%20%22https%3A%2F%2Fmcp.membase.so%2Fmcp%22%7D) [](./LICENSE) [](./CONTRIBUTING.md) [](https://discord.gg/vHgtDd6UTK)
Use cases
Most AI tools forget everything the moment a chat ends. Context you've already explained — your stack, your preferences, decisions you made last week — has to be re-explained every session, and it never carries across to a different tool. With Membase, your agents share one persistent memory:
- Persistent project context — your agent remembers your stack, conventions,
and past decisions instead of asking again every session.
- Cross-tool continuity — capture something in Claude Code and recall it in
Cursor or Codex, because they share one memory.
- Long-running work — pick up a multi-day task with the relevant history
pulled back into context automatically.
- Personal knowledge — save facts, preferences, and notes once and let any
connected agent retrieve them on demand.
Installation
One command, every detected client (Claude Code, Cursor, Codex):
npx plugins add aristoapp/membase-plugin-mcp
Or Claude Code alone, via its plugin marketplace:
claude plugin marketplace add aristoapp/membase-plugin-mcp
claude plugin install membase@membase-plugins
Per-client manual setup below. Every client connects to the same hosted MCP server: https://mcp.membase.so/mcp.
Claude Code
claude mcp add --transport http membase https://mcp.membase.so/mcp
Want auto-capture and cross-session handoff too? Install the Membase plugin (a bundled MCP server plus hooks) instead — the repo root is the plugin package; see the install commands above or [clients/claude](clients/claude).
Full guide: [docs/install/claude.md](docs/install/claude.md)
Cursor
Click to install:
[](https://cursor.com/en/install-mcp?name=membase&config=eyJ1cmwiOiJodHRwczovL21jcC5tZW1iYXNlLnNvL21jcCJ9)
Or add it by hand to .cursor/mcp.json (this project) or ~/.cursor/mcp.json (all projects):
{
"mcpServers": {
"membase": {
"url": "https://mcp.membase.so/mcp"
}
}
}
Full guide: [docs/install/cursor.md](docs/install/cursor.md)
Codex CLI
codex mcp add membase --url https://mcp.membase.so/mcp
codex mcp login membase
Or add it to ~/.codex/config.toml (global) or .codex/config.toml (this project):
[mcp_servers.membase]
url = "https://mcp.membase.so/mcp"
Full guide: [docs/install/codex.md](docs/install/codex.md)
VS Code
Click to install:
[](https://insiders.vscode.dev/redirect/mcp/install?name=membase&config=%7B%22type%22%3A%20%22http%22%2C%20%22url%22%3A%20%22https%3A%2F%2Fmcp.membase.so%2Fmcp%22%7D)
Or add it to your MCP config (.vscode/mcp.json):
{
"servers": {
"membase": {
"type": "http",
"url": "https://mcp.membase.so/mcp"
}
}
}
Hermes Agent
Add the server under mcp_servers in ~/.hermes/config.yaml:
mcp_servers:
membase:
url: "https://mcp.membase.so/mcp"
Prefer a native integration? Hermes also ships a Python provider package — see [clients/hermes](clients/hermes).
Full guide: [docs/install/hermes.md](docs/install/hermes.md)
OpenClaw
Remote MCP (simplest). Add Membase to your OpenClaw MCP config:
{
"mcpServers": {
"membase": {
"url": "https://mcp.membase.so/mcp"
}
}
}
Native plugin (richer — auto-capture and recall). From an OpenClaw checkout:
openclaw plugins install --link ./clients/openclaw
openclaw plugins enable openclaw-membase
openclaw gateway restart
Full guide: [docs/install/openclaw.md](docs/install/openclaw.md)
Other MCP hosts (ChatGPT, Gemini CLI, OpenCode, Poke, …)
Any MCP-capable host can connect with the generic remote config plus the OAuth prompt on first use:
{
"mcpServers": {
"membase": {
"url": "https://mcp.membase.so/mcp"
}
}
}
Tools
Every connector reaches the same hosted MCP tool set:
add_memory · search_memory · add_wiki · search_wiki · update_wiki · delete_wiki · get_current_date
Clients with a native runtime (Claude Code, OpenClaw, Hermes) make memory automatic: just work, and your sessions are captured, recalled, and handed off for you. Details in each client's install guide.
Anything important, save it yourself and pull it back later — plain language is enough, the agent calls the tools for you:
Remember that we deploy from the release branch, never from main.
What did we decide about the auth flow last week?
Save this: the staging database resets every night at 02:00 UTC.
How it works
Connectors talk to a stable Membase Context API.
Client plugin or MCP config ← per-client adapter (clients/*)
│
▼
Shared connector core ← packages/core, packages/connector-sdk
│
▼
Membase Context API ← stable public surface
│
▼
Private Membase memory engine ← storage, graph, ranking (not in this repo)
Client-specific behavior stays in clients/*; shared behavior lives in packages/*.
For the full design rationale, see [docs/architecture.md](docs/architecture.md) and the "where does X live" map in [MAP.md](MAP.md).
> Note: This repository is the connector/integration layer only. The > Membase Context API, memory engine, and their supporting services are a > separate, private system and are not part of this repo.
Contributing
Contributions are welcome — new connectors, bug fixes, docs, performance optimization. This is a pnpm monorepo (Node.js 20+, pnpm 11+):
pnpm install
pnpm test # runtime + contract suites
pnpm check # the same gate CI runs on your PR
Details in [CONTRIBUTING.md](CONTRIBUTING.md); please also review our [Code of Conduct](CODEOFCONDUCT.md).
Security
For security issues, see [SECURITY.md](SECURITY.md) for how to report a vulnerability, and [docs/security.md](docs/security.md) for the connector secret-handling and redaction model.
License
Released under the [MIT License](LICENSE).
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: aristoapp
- Source: aristoapp/membase
- License: MIT
- Homepage: https://membase.so/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.