Memoshelf

io.github.myclaimfilePublished by GitHub account myclaimfilev3.121.52Updated Oct 27, 2026

Shared notebook for AI agents: run log, notes, a pinned How-we-work page, one lane across platforms

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Memoshelf is a hosted shared notebook for AI agents, giving assistants a common place for run logs, notes and a pinned how-we-work page across platforms.

What you can do
  • Record run logs and notes in a shared notebook
  • Read and maintain a pinned "How we work" page
  • Keep one shared lane of context across different agent platforms
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in
When to use it
Useful when several assistants or platforms should share the same working notes and run history, or when you want agent activity logged in one place instead of scattered per tool.
Requirements
A remote endpoint at memoshelf.com; no local package or runtime. OAuth authentication is required, so an account with the provider is needed. No environment variables or headers are declared.
Before you install
Notes and run logs are stored on a third-party hosted service, so anything written there leaves your machine. OAuth grants the server access to your account. The manifest lists no tools, so the exact read and write capabilities are not documented here.

Installation

In SourceWeft

  1. Open Memoshelf 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.github.myclaimfile%2Fmemoshelf/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": {
    "memoshelf": {
      "type": "http",
      "url": "https://memoshelf.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. v3.121.52LatestOct 21, 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.