Marrow

id.marrowPublished by marrow.idOfficial publisherv1.0.10Updated Oct 24, 2026

Evidence-grounded, graph-connected, correctable memory for agents.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Marrow gives an assistant an evidence-grounded, graph-connected, correctable memory store it can query and update.

What you can do
Marrow is a memory service for agents, described as evidence-grounded, graph-connected and correctable. It is reachable as a remote endpoint over streamable HTTP, and a local npm package acts as a compatibility adapter over stdio. The registry listing does not enumerate individual tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs persistent, connected memory across sessions rather than a single conversation's context, and when you want that memory to be correctable rather than append-only. It is less relevant for one-off tasks that need no recall.
Requirements
Either a remote endpoint connection or a local process via the npm package. The local adapter requires the secret MARROW_API_KEY. No other accounts, headers or network details are declared.
Before you install
The local adapter requires the secret MARROW_API_KEY; treat it as a credential and avoid exposing it in logs or shared configuration. Because the server stores and corrects memory, assume it can write, change and delete stored content. No tool list is published, so review what it can modify before pointing it at sensitive material.

Installation

In SourceWeft

  1. Open Marrow in the dashboard and add it to a workspace.
  2. 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/id.marrow%2Fmarrow/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.

{
  "mcpServers": {
    "marrow": {
      "type": "http",
      "url": "https://mcp.marrow.id/"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.10LatestSep 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Marrow integrations