Memroot

io.github.memrootPublished by GitHub account memrootv1.0.0Updated Oct 30, 2026

Persistent engineering memory designed to follow developers across coding agents.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Memroot is a remote MCP server providing persistent engineering memory that follows developers across coding agents.

What you can do
  • The listing gives no tool list, so capabilities are known only from its one-line description.
  • It is described as persistent engineering memory for developers.
  • That memory is meant to carry across different coding agents rather than stay tied to one tool.
  • No further detail on reading, writing or searching that memory is provided.
When to use it
Consider it if you work with several coding agents and want context or engineering knowledge to persist between them instead of being re-established each session.
Requirements
A remote MCP endpoint at api.memroot.dev over streamable HTTP; OAuth authentication is required. No packages, environment variables or headers are declared.
Before you install
It stores engineering memory in a third-party hosted service, so code-related context you share is sent to that provider. OAuth grants access to your account there; review what the service retains before connecting.

Installation

In SourceWeft

  1. Open Memroot in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.memroot%2Fmemroot/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "memroot": {
      "type": "http",
      "url": "https://api.memroot.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.