MemScope

ai.memscopePublished by memscope.aiOfficial publisherv0.1.0Updated Nov 6, 2026

Governed organizational memory for AI: recall returns only what the signed-in person may see.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

MemScope is a remote MCP server that gives an assistant governed organizational memory, returning only the memories the signed-in person is allowed to see.

What you can do
  • Recall organizational memory through the server's recall capability, filtered by the signed-in person's permissions.
  • No tool list is published, so the exact set of operations is not documented in the supplied material.
  • Access is tied to an OAuth sign-in, so results reflect the identity of the person who authorized the connection.
When to use it
Consider it when an assistant should draw on shared company or team knowledge while respecting per-person access rules, rather than a single shared memory store visible to everyone.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address; no local package or runtime is needed. OAuth authentication is required, so the user must sign in and authorize the connection. No environment variables or headers are declared.
Before you install
The server holds organizational memory and enforces visibility by signed-in identity, so the account used for authorization determines what the assistant can retrieve; connect with the intended account. Memory content is sent to the provider's hosted service. The published material lists no tools, so review what the server can read or write before relying on it.

Installation

In SourceWeft

  1. Open MemScope 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.memscope%2Fmemscope/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": {
    "memscope": {
      "type": "http",
      "url": "https://mcp.memscope.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. v0.1.0LatestNov 6, 2026

Score

83% 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
  • 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.