Memnode

dev.memnodePublished by memnode.devOfficial publisherv0.1.0Updated Oct 24, 2026

Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Memnode gives an AI assistant persistent, inspectable memory with lineage and correction, through a hosted remote MCP endpoint.

What you can do
Memnode is a hosted memory service for AI agents, reached over a remote streamable HTTP MCP endpoint. According to the registry description, it provides persistent, inspectable memory that tracks lineage and supports correction. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs memory that persists across sessions and can be inspected or corrected rather than discarded. It suits workflows where tracing where a stored memory came from matters.
Requirements
A remote MCP client connecting to the hosted endpoint at api.memnode.dev over streamable HTTP. OAuth authentication is required. No environment variables, headers or local packages are declared.
Before you install
Access is tied to an OAuth account with a third-party hosted service, so stored memory content is sent to and kept by that provider. Review what data you allow the assistant to persist before connecting.

Installation

In SourceWeft

  1. Open Memnode 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/dev.memnode%2Fmemnode/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": {
    "memnode": {
      "type": "http",
      "url": "https://api.memnode.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. v0.1.0LatestSep 16, 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.