Memory

com.humauxPublished by humaux.comOfficial publisherv0.3.0Updated Oct 24, 2026

Persistent long-term memory for AI agents: semantic search, knowledge graph, and task canvas.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP service giving AI assistants persistent long-term memory with semantic search, a knowledge graph, and a task canvas.

What you can do
Memory is a hosted MCP endpoint that provides persistent long-term memory for AI agents. According to its registry description, it offers semantic search over stored memories, a knowledge graph for connected information, and a task canvas. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to remember information across sessions, recall related context by meaning rather than exact keywords, or keep track of tasks and linked knowledge over time. It is less relevant for one-off, stateless conversations.
Requirements
A remote streamable HTTP endpoint at humaux.com; no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The service is remote and requires OAuth sign-in, so anything stored is sent to and kept by a third party. Memory content may include sensitive or personal information; review what the assistant is allowed to persist before use. No tools, retention policy, or deletion behavior are documented in the provided material.

Installation

In SourceWeft

  1. Open Memory 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.humaux%2Fmemory/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": {
    "memory": {
      "type": "http",
      "url": "https://humaux.com/memory/mcp"
    }
  }
}

README

This repository has no README.

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.0LatestSep 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 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.

  • License10 pts

    Declare a license in the repository or the registry entry.