
memsprout
com.memsproutPublished by memsprout.comOfficial publisherv0.1.0Updated Oct 24, 2026
shared AI-context layer for teams — persistent memory your agents search and update over MCP
Overview
Remote MCP server giving a team's AI agents a shared, persistent memory they can search and update across sessions, models and clients.
- What you can do
- Search and update a shared team knowledge base over MCP, so context carries across sessions, models and clients.
- Every connected agent and tool reads and writes the same memory, keeping team context consistent.
- Ships setup paths for Claude Code, claude.ai and Claude Desktop, Cursor, Codex and other MCP clients.
- Includes a usage skill that tells an agent when and how to use the memory tools.
- Offers an installer that detects installed MCP clients and can scaffold team files into a repo.
- When to use it
- Useful when several agents or teammates need one durable place for project context instead of repeating it in each session, or when you want memory shared across different clients and models.
- Requirements
- A memsprout account created on the vendor site before connecting; the OAuth sign-in only signs in existing accounts. A remote MCP client pointed at the streamable HTTP endpoint with OAuth 2.1 support. Network access to the vendor's server.
Installation
In SourceWeft
- Open memsprout in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.memsprout%2Fmemsprout/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"memsprout": {
"type": "http",
"url": "https://mcp.memsprout.com/mcp"
}
}
}README
memsprout for AI agents
memsprout is a shared AI-context layer for teams —
persistent memory your agents search and update over MCP. Every agent and
tool you connect reads and writes the same knowledge base, so context
survives across sessions, models, and clients. This repo packages the
connection two ways: a Claude Code plugin (remote MCP server + a usage
skill) and a standalone Agent Skill that works
in any client that reads SKILL.md.
Before you install
Create an account at memsprout.com first. The OAuth sign-in that opens when a client first connects does not create accounts — it only signs in existing ones.
One-command setup
Detects your installed MCP clients (Claude Code, Codex, Gemini CLI,
Cursor), wires each selected one to the server, and offers to scaffold
the team files into your repo. Non-destructive, idempotent, stores no
credentials. Source in installer/. Not yet published to
npm — until it is, use the per-client instructions below.
Claude Code
The plugin adds the memsprout MCP server and the using-memsprout skill.
The first connection opens the browser OAuth flow.
claude.ai and Claude Desktop
Add memsprout as a custom connector: Settings → Connectors → Add custom connector, with the server URL below. Sign in when the memsprout consent screen opens.
Agent Skill via skills.sh
Installs the using-memsprout skill, which teaches your agent when and
how to use memsprout's tools. You still need the MCP server connected
(see below) — the skill describes the doctrine; the server provides the
tools.
Cursor
The cursor/ directory has copy-in files for both motions:
merge cursor/mcp.json into ~/.cursor/mcp.json for yourself, or commit
it as .cursor/mcp.json plus the cursor/rules/memsprout.mdc project
rule to your team's repo so every teammate's Cursor shares the same
memory. See cursor/README.md.
Codex
The Codex CLI, IDE extension, and ChatGPT desktop app share
~/.codex/config.toml, so this one command wires all three. For team
setup, append the client-agnostic
codex/AGENTS-snippet.md to your repo's
AGENTS.md so every AGENTS.md-reading agent follows the team's memory
doctrine. See codex/README.md.
Any other MCP client
Point your client at the remote server:
Streamable HTTP with OAuth 2.1 — clients that support MCP authorization discover the sign-in flow automatically. Per-client wiring instructions (Codex, Gemini CLI, Cursor, and more) are at memsprout.com/connect.
What's in this repo
Support
- Product: memsprout.com
- Issues with this plugin or skill: open an issue in this repo
Source: README.md at commit f4be3a3
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts