knowsme

dev.knowsmePublished by knowsme.devOfficial publisherv1.0.1Updated Oct 24, 2026

One memory for you and your AI agents, shared by ChatGPT, Claude, Gemini, Grok, Codex and Cursor.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

knowsme is a remote MCP memory service that gives an assistant a shared memory across ChatGPT, Claude, Gemini, Grok, Codex and Cursor.

What you can do
  • Store and recall a shared memory that persists across AI assistants and agents
  • Keep one memory usable from several clients, including ChatGPT, Claude, Gemini, Grok, Codex and Cursor
  • Connect over a remote streamable HTTP endpoint rather than a local package
When to use it
Use it when you want context to carry over between different AI assistants and coding agents instead of being trapped in one chat or tool.
Requirements
A remote MCP endpoint at mcp.knowsme.dev reached over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
Sign-in is via OAuth, so the service holds an account tied to your memory. The description does not state what is stored, how long it is kept, or which third parties can read it; treat anything you save as shared across every connected assistant.

Installation

In SourceWeft

  1. Open knowsme 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/dev.knowsme%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": {
    "knowsme": {
      "type": "http",
      "url": "https://mcp.knowsme.dev/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

2
  1. v1.0.1LatestOct 6, 2026
  2. v1.0.0Sep 24, 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.