StudioMeyer Memory

io.studiomeyerPublished by studiomeyer.ioOfficial publisherv3.41.0Updated Oct 24, 2026

Bi-temporal AI memory. 56 tools, knowledge graph, semantic search. EU-hosted, free tier.

The publisher's own server: StudioMeyer Crew

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Remote bi-temporal AI memory server with a knowledge graph and semantic search, giving an assistant persistent recall across sessions.

What you can do
  • Store and recall memories with bi-temporal tracking, so facts can be kept with their valid-time context.
  • Search stored knowledge semantically rather than by exact keywords.
  • Organize and relate memories in a knowledge graph.
  • Exposes a broad tool set (56 tools) covering memory and graph operations.
When to use it
Useful when you want an assistant to remember information across conversations and retrieve it later by meaning, and when you prefer an EU-hosted managed service over running your own memory store.
Requirements
Remote streamable HTTP endpoint at memory.studiomeyer.io; OAuth authentication is required. No environment variables or headers are declared. A free tier is offered.
Before you install
Memories are stored on a third-party EU-hosted service, so anything the assistant saves leaves your machine; avoid storing secrets or sensitive personal data. OAuth grants the server access under your account, and the tool set can write and change stored memories.

Installation

In SourceWeft

  1. Open StudioMeyer 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/io.studiomeyer%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": {
    "studiomeyer-memory": {
      "type": "http",
      "url": "https://memory.studiomeyer.io/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. v3.41.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.

Other Studiomeyer integrations