OwlMem

com.owlmemPublished by owlmem.comOfficial publisherv0.80.4Updated Nov 3, 2026

Shared memory and teamwork for AI agents: knowledge base, memories, tasks, encrypted vault.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

OwlMem is a remote MCP server giving AI agents shared memory, a knowledge base, tasks and an encrypted vault for teamwork.

What you can do
  • Store and recall shared memories across agents and sessions
  • Keep and query a shared knowledge base
  • Create and track tasks for agent teamwork
  • Use an encrypted vault for sensitive items
  • Connect over a hosted remote endpoint with OAuth sign-in
When to use it
Useful when several agents or sessions need to share context, notes and tasks instead of starting from scratch, or when you want a hosted memory layer without running your own server.
Requirements
A remote MCP endpoint at mcp.owlmem.com over streamable HTTP; OAuth authentication is required, so an OwlMem account is needed. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your OwlMem account, and stored memories, knowledge and tasks are shared with connected agents. The vault is described as encrypted, but the input gives no details on key handling. No tool list is published, so review what it can read or change after connecting.

Installation

In SourceWeft

  1. Open OwlMem 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.owlmem%2Fowlmem/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": {
    "owlmem": {
      "type": "http",
      "url": "https://mcp.owlmem.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

5
  1. v0.80.4LatestNov 3, 2026
  2. v0.77.6Nov 1, 2026
  3. v0.75.1Nov 1, 2026
  4. v0.74.0Oct 31, 2026
  5. v0.16.0Oct 24, 2026

Score

72% 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

    Publish an icon in the registry entry.

  • Documentation15 pts
  • 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.