The context layer for AI-assisted development.
Everything that happens in your projects, connected, current and shared with your team and your agents.
Presigned single PUTs time out on slow connections for large files. Files over 10 MB use S3 multipart; hard limit of 50 MB enforced when signing.
Proxying uploads through the API saturated the instances. The client now uploads straight to S3; the API only signs URLs and stores metadata. Consequence: bucket CORS must be kept in sync per environment.
Retry storms from the cron job were hitting partner rate limits. Moving delivery to a queue with exponential backoff and a dead-letter queue.
Context that stays current, connected and shared
Current
Replaced entries archive themselves. Your agents work with what's current.
Connected
Every entry links to others and to your code: commits, PRs and issues.
Shared
Invite your team to a scope. People and agents read and contribute to the same context, each with their own permissions.
One scope for people and agents
Each one gets its own permission: read-only, or read and write.
Features
Outdated entries archive themselves
When an entry replaces another, the old one stops showing up in searches.
Everything connected
Relations between entries: what caused what, what implements what.
Linked to your code
References to a commit, PR, issue, branch or URL.
Works where you code
Claude Code, Cursor and VS Code, via MCP.
How it works
Log it
Write down what you did or decided, in free text, in seconds. Pick the scope: work, a specific client, a side project. Attach files if you need to.
Ask
"What did we decide about attachments?" — mem4dev searches your entries by meaning, not word by word, and answers citing where each fact came from.
Connect your AI environment
Add mem4dev as an MCP server in your editor. Your AI assistant reads the project context and writes new entries while you code, without opening the app.
claude mcp add --transport http mem4dev https://app.mem4dev.com/mcp
{ "mcpServers": { "mem4dev": { "url": "https://app.mem4dev.com/mcp" } } }
{ "servers": { "mem4dev": { "type": "http", "url": "https://app.mem4dev.com/mcp" } } }
⎿ The first time, your browser opens the OAuth authorization screen.
Connected entries
Every relation has a type: replaces, caused_by, implements, refines, continues and relates_to. When an entry replaces another, the old one is archived.
Linked to your code
An entry points to commits, pull requests, issues, branches and URLs. Your assistant creates relations with link_entries and follows them with get_related_entries.
Real example: while this very page was being written with Claude Code, the agent had the mem4dev MCP connected and could query and log directly to the project's log. This isn't a demo — it's how it's used every day.
For developers working on more than one front at a time
Developers who code with AI
Your context is the memory your AI assistant doesn't have between sessions by default.
Freelancers and technical consultants
One scope per client, with its history at hand when they ask for it.
Tech leads and engineering managers
The team's decisions, connected and current, in one place.
Development teams
Share scopes with other people on your team today, on Free and Individual. The Teams plan, with an organization account, is coming soon.
Your projects never mix. 100% isolated scopes.
The text of your entries is encrypted in the database. All traffic travels over HTTPS.
Your AI assistants connect through standard OAuth. You authorize them and revoke them whenever you want.
Per-scope permissions: read-only, or read and write, for people, API keys and AI assistants.
Export a whole scope to JSON. You get the download link by email.
Start free. Scale when you need to.
Free
To try it for real
1 scope, up to 1,000 entries, 1,000 interactions a month and 100 MB of attachments. Sharing is included: 1 person per scope and 1 scope shared by other accounts. MCP and API included, with no feature restrictions: the limit is on volume, not features.
Start freeIndividual
For those who already found the value
From USD 7.99 a month
Up to 10 scopes, 10,000 entries, 10,000 interactions a month and 1 GB of attachments. Sharing is included: up to 10 people per scope and up to 10 scopes shared by other accounts. If you need more, you expand capacity within the same plan.
Choose IndividualTeams coming soon
For teams that share work
When it launches, Teams will add an organization account with a verified company domain, an admin role and scopes that belong to the company, not to each person.
Today you can collaborate on Free and Individual. The limits of a shared scope are those of its owner's plan.
FAQ
What is MCP and why does it matter?+
It's an open standard that lets AI assistants (Claude, Cursor, etc.) use external tools securely. With mem4dev connected, your assistant can read your project context and save new entries directly.
Does my data get mixed with other users' or across my own scopes?+
No. Every account and every scope is isolated by design — it's the product's number one rule.
Can I try it without a credit card?+
Yes, the free plan doesn't ask for a payment method.
Can I share a scope with my team?+
Yes. You can share a scope with other people on any plan (Free allows inviting 1 person per scope; Individual, up to 10); the limits are set by the plan of the scope's owner. The Teams plan, for organizations, is coming soon.
What counts as an interaction, and what happens if I reach a limit?+
Every API call, every MCP call and every question in Ask counts as one interaction; what you do from the web app does not count. If you reach the entries limit only creating more is blocked. If you reach the interactions limit, the API, MCP and Ask pause until it renews, and in the web app you can keep reading and editing. Nothing is deleted.
If I share a scope, do the other people's interactions count against my limit or theirs?+
Yours. Everything done inside a shared scope (saving entries, querying, from the web app, the API or MCP) counts against the plan of the scope's owner, not the invited person's. The same goes for the entries and attachments limits. Invited people keep using their own plan for the scopes they own.
Can I export my data?+
Yes. From Scopes you can export a whole scope to JSON: we email you a download link. Only the scope's owner can export it.
How do I control what my AI can do in my scopes?+
When you connect an assistant over MCP you choose read-only or read-and-write, and all your scopes or just some. With the API you use keys with per-scope permissions. You can revoke any access whenever you want.
What happens to my data if I delete my account?+
You have 30 days to change your mind: if you sign in again within that period, the deletion is cancelled. After that, your entries, attachments and search index are permanently erased.
Does mem4dev have an MCP server?+
Yes. mem4dev has a native MCP server at https://app.mem4dev.com/mcp that works with Claude Code, Claude Desktop, Cursor, VS Code and any MCP client. It uses OAuth 2.1 with PKCE, so you authorize the client in your browser, choose read-only or read-and-write access, and pick which scopes it can reach.
How do I connect Claude Code to mem4dev?+
Run: claude mcp add --transport http mem4dev https://app.mem4dev.com/mcp. The first time you use it, a consent screen opens where you log in and authorize the connection.
Does mem4dev have an API?+
Yes. A REST API at https://app.mem4dev.com/api/v1 with API keys that are read-only or read-and-write per scope. It supports logging, reading, searching, editing and deleting entries. See https://mem4dev.com/docs/.
Stop explaining what you did. Start asking it.
Create free accountContact
Write to us and we will reply by email.