OneAIMemory

io.github.AmxnCodePublished by GitHub account AmxnCodev1.0.0Updated Oct 24, 2026

Cross-device AI memory with encrypted activity capture and context handoff between AI tools

The publisher's own server: Memory.fit

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant cross-device AI memory, with encrypted activity capture and context handoff between AI tools.

What you can do
Provide a shared memory layer that an assistant can use across devices and across different AI tools, so context carries over between sessions and applications. Capture activity in encrypted form as part of that memory. Hand off context from one AI tool to another. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth considering when you work with several AI tools or devices and want context and memory to follow you between them, rather than starting each session from scratch.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address; no local package, environment variables or headers are declared. The manifest declares no authentication, so account or sign-in requirements are not documented.
Before you install
The service captures activity and stores it as memory, so consider what personal or work data would be sent to a third-party host and how it is retained. The manifest declares no authentication, so verify how access to your memory is protected before relying on it.

Installation

In SourceWeft

  1. Open OneAIMemory in the dashboard and add it to a workspace.
  2. 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.AmxnCode%2Foneaimemory/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.

{
  "mcpServers": {
    "oneaimemory": {
      "type": "http",
      "url": "https://mcp.oneaimemory.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations