About Memctl
Memctl is an MCP server published by memctl in the Developer Tools category: shared, persistent memory for AI coding agents. One project brain across machines and IDEs. Perfect for projects and teams. It has been installed 0 times through Conduid.
The repository has 2 stars and 0 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx memctlThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Memctl
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
What is mem/ctl?
mem/ctl is a cloud MCP server that gives AI coding agents shared, persistent memory scoped to projects and organizations. Claude Code, Cursor, Windsurf, Cline, Roo Code, Codex, OpenCode, and any MCP-compatible agent can read and write to the same project context.
Your team shares one brain. Every agent knows the architecture, conventions, decisions, and constraints without repeating yourself.
Quick start
npx memctl auth
npx memctl init
The init wizard detects your IDE and writes the MCP config automatically. Or configure manually:
{
"mcpServers": {
"memctl": {
"command": "npx",
"args": ["-y", "memctl@latest"],
"env": {
"MEMCTL_ORG": "<org-slug>",
"MEMCTL_PROJECT": "<project-slug>"
}
}
}
}
Agent support
| Agent | Config file | Init shortcut | Generate |
|---|---|---|---|
| Claude Code | .mcp.json |
memctl init --claude |
memctl generate --claude |
| Cursor | .cursor/mcp.json |
memctl init --cursor |
memctl generate --cursor |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
memctl init --windsurf |
memctl generate --windsurf |
| Cline | .vscode/mcp.json |
memctl init --cline |
memctl generate --cline |
| Roo Code | .vscode/mcp.json |
memctl init --roo |
memctl generate --roo |
| Codex | codex.json |
memctl init --codex |
memctl generate --codex |
| OpenCode | opencode.json |
memctl init --opencode |
memctl generate --opencode |
All agents, all at once:
npx memctl init --all
MCP tools
mem/ctl exposes 11 tools to connected agents:
| Tool | What it does |
|---|---|
memory |
Store, get, search, list, update, delete memories with dedup and tagging |
memory_advanced |
Batch get, find similar, diff, merge, and rename keys |
memory_lifecycle |
Archive, restore, history, bulk tag/untag, and capacity checks |
context |
Bootstrap project context, delta sync, smart retrieval, rules evaluation |
context_config |
Manage typed project guidance (coding style, architecture, constraints) |
session |
Session lifecycle, conflict claims, and rate status |
activity |
Memos, activity log, impact analysis |
branch |
Branch-scoped context and implementation plans |
repo |
Repository structure analysis |
org |
Organization info and project listing |
import_export |
Bulk import/export memories as JSON |
Plus 7 resources and 3 prompts for richer agent integration.
How it works
- Agent connects to
memctlvia MCP (stdio transport) - On startup, the agent bootstraps project context (conventions, architecture, constraints)
- During the session, the agent reads and writes memories as needed
- All agents on the team share the same project memory
- Session tracking prevents write conflicts across concurrent agents
Features
- Project-scoped memory with key-value storage and rich metadata
- Hybrid search combining FTS5 full-text and vector embeddings (all-MiniLM-L6-v2)
- Smart deduplication that warns, skips, or merges similar content
- Branch context for tracking implementation plans per git branch
- Session management with conflict detection and automatic handoff
- Activity memos for cross-session communication between agents
- Content quality filter that blocks noise (shell dumps, raw diffs, JSON blobs)
- Typed project guidance for architecture, coding style, folder maps, and constraints
- Organization defaults that apply across all projects
- Role-based access with owner, admin, and member roles
- Self-hostable with Docker
Tech stack
| Layer | Technology |
|---|---|
| Runtime | Node.js + TypeScript |
| Monorepo | pnpm workspaces + Turborepo |
| Web | Next.js 15 (App Router) |
| Database | Turso (libSQL) + Drizzle ORM |
| Search | FTS5 + vector embeddings |
| Auth | better-auth (GitHub OAuth + magic link) |
| Payments | Stripe |
| MCP | @modelcontextprotocol/sdk |
| Testing | Vitest |
Project structure
apps/web/ Next.js dashboard + REST API
packages/cli/ MCP server + CLI (published to npm as "memctl")
packages/db/ Drizzle ORM schema + migrations
packages/shared/ Types, validators, constants
Development
git clone https://github.com/memctl/memctl.git
cd memctl
pnpm install
pnpm dev
See DOCKER.md for Docker-based development and CONTRIBUTING.md for contribution guidelines.
Useful commands
pnpm dev # Dev server (Turbopack)
pnpm lint # ESLint all packages
pnpm format:check # Prettier check
npx vitest run # Run tests
pnpm db:push # Push schema to DB
pnpm db:generate # Generate migrations
pnpm db:migrate # Run migrations
Self-hosting
Set SELF_HOSTED=true and NEXT_PUBLIC_SELF_HOSTED=true to run your own instance. This disables billing and unlocks all plan limits.
docker build --build-arg NEXT_PUBLIC_APP_URL=https://your-domain.com -t memctl-web .
See DOCKER.md for the full self-hosting guide.
Documentation
- Docs -- full documentation
- Architecture -- system design and infrastructure
- Docker -- Docker setup for dev and production
- Contributing -- how to contribute
- Security -- security policy
License
README mirrored from the source repository 8 hours ago. The original is authoritative.