Chiron

com.chironmemoryPublished by chironmemory.comOfficial publisherv0.15.4Updated Nov 14, 2026

Shared team memory for AI assistants. Private by default; teammates see only what you choose.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Chiron gives an AI assistant long-term memory across sessions and projects, with optional sharing of selected memories with a team.

What you can do
  • Remember what you have told the assistant and worked on together, across sessions and projects
  • Bring related memories to mind as you type
  • Keep memories private on your own computer by default
  • Share only chosen memories with teammates through a team Chiron server
  • Optionally back up private memories to the team server when enabled in the Chiron app
When to use it
Useful when you want an assistant that carries context between conversations and projects instead of starting fresh, or when a small team wants a shared memory that each person controls.
Requirements
A remote endpoint or the local Chiron app installed via the provided setup guide; OAuth authentication is required. Needs Claude Code and about 500 MB of free disk space on macOS, Windows or Linux; no admin password or Docker.
Before you install
Private memories stay local unless private backup is turned on in the Chiron app, after which they go to the team's Chiron server. Shared memories are visible to teammates. The beta Windows app is not code-signed, so Windows may warn about an unknown publisher; read the beta notes before joining.

Installation

In SourceWeft

  1. Open Chiron 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/com.chironmemory%2Fchiron/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": {
    "chiron": {
      "type": "http",
      "url": "https://api.chironmemory.com/mcp"
    }
  }
}

README

Chiron beta

Chiron gives your Claude a long-term memory. It remembers what you've told it and worked on together, across sessions and projects, and brings related memories to mind as you type.

Everything runs on your own computer. Private memories stay on it. They go to your team's Chiron server only if you turn on private backup in the Chiron app. Your team sees only what you choose to share.

Installing

You don't need to do this by hand. Open Claude Code and say:

Install Chiron by following https://github.com/Mad-Science-Software/chiron-beta/blob/main/docs/setup.md

On a Mac, Windows or Linux it takes about 5 minutes and installs the Chiron app: no admin password, no Docker. You'll need Claude Code and about 500 MB of free disk space. On Windows the app isn't code-signed yet, so Windows may call it an unknown publisher.

Before installing, read BETA.md: it's short, and it explains what taking part means.

Feedback

This is a beta, so things will break. Please email anything that goes wrong, feels off or surprises you to [email protected]. Screenshots or a copy of what Claude said help a lot. Never send your memories themselves.

Source: README.md at commit b0e9933

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.15.4LatestNov 14, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.