Nuramem

ai.nuramemPublished by nuramem.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Cross-model memory for people and teams: one memory every AI you use loads at session start.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Nuramem is a remote, OAuth-protected memory service that gives an AI assistant a shared memory loaded at session start across the models you use.

What you can do
Provides a cross-model memory layer for individuals and teams, so context saved in one AI session can be available to others at session start. The manifest lists no tools, so the exact operations are not documented here; expect the assistant to read and write memory entries through the connection. Access is through a hosted remote endpoint rather than a local package.
When to use it
Worth considering if you work across several AI assistants or models and want continuity of context between them, or if a team wants one shared memory rather than per-tool histories.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP, plus an OAuth sign-in with a Nuramem account. No local runtime, packages, environment variables or headers are declared.
Before you install
The service stores your memory content on a third party's servers, so anything you let the assistant save leaves your machine and is retained by the provider. OAuth grants the server access under your account. Because no tools are listed, review what it can read or change after connecting before relying on it.

Installation

In SourceWeft

  1. Open Nuramem 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.nuramem%2Fnuramem/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": {
    "nuramem": {
      "type": "http",
      "url": "https://mcp.nuramem.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. v1.0.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.