Memlo

ai.memloPublished by memlo.aiOfficial publisherv1.0.0Updated Oct 31, 2026

Hosted memory for AI agents over MCP. One memory shared by all your agents.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Memlo is a hosted memory service for AI agents, reached over MCP, that lets assistants share one memory across all of your agents.

What you can do
  • The listing names no individual tools, so capabilities come from the short description only.
  • It provides hosted memory that AI agents can use through MCP.
  • That memory is described as one store shared by all of your agents, rather than per-agent memory.
  • No details are given on how memories are written, read, searched or scoped.
When to use it
Consider it when you run several AI agents or clients and want them to draw on a common memory instead of separate, isolated context. It suits users who prefer a hosted service over running their own memory backend.
Requirements
A remote MCP endpoint at memlo.ai over streamable HTTP. Authentication is required and uses OAuth, so you need a Memlo account and a client that supports OAuth for MCP connections. No environment variables or headers are declared.
Before you install
Because one memory is shared by all your agents, anything stored may be visible to every connected agent and client. The service is hosted by a third party, so stored memory content leaves your machine. No tool list is published, so review what it can read or write after connecting.

Installation

In SourceWeft

  1. Open Memlo 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/ai.memlo%2Fmemlo/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": {
    "memlo": {
      "type": "http",
      "url": "https://memlo.ai/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 31, 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.