Hebby Memories

com.hebby-memoriesPublished by hebby-memories.comOfficial publisherv0.3.4Updated Nov 6, 2026

Long-term memory for AI agents: graph memory with Hebbian learning, shared by Claude, Codex and co.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP server giving AI assistants long-term graph memory with Hebbian learning, shared across Claude, Codex and other agents.

What you can do
  • Provides long-term memory for AI agents, stored as a graph rather than flat notes.
  • Applies Hebbian learning, so connections between memories strengthen through use.
  • Shares one memory store across different assistants such as Claude and Codex.
  • No individual tools are documented in the supplied listing, so exact operations are not described.
When to use it
Useful when you want an assistant to remember context across sessions and across different agent clients, rather than starting from scratch each time.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth authentication is required. No packages, environment variables or headers are declared.
Before you install
The server stores long-term memory of your conversations and context on a third-party hosted service, shared across connected agents; consider what personal or project information you let it retain. Access is granted through OAuth, so review the permissions requested at sign-in.

Installation

In SourceWeft

  1. Open Hebby Memories 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/com.hebby-memories%2Fhebby/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": {
    "hebby-memories": {
      "type": "http",
      "url": "https://mcp.app.hebby-memories.com/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.3.4LatestNov 6, 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.