Open source · Apache-2.0 · MCP

Your AI's memory is a Git repo you own.

OpenStore gives any AI a durable, user-owned store: a private GitHub repository of plain Markdown that it reads and writes with bash-like tools — grep, cat, write, git_log. OpenStore does not persist your notes. GitHub holds the repository and its history.

Live for Claude Code. GitHub sign-in and read/write tools are verified. Claude.ai and ChatGPT connector verification is still in progress.

Get started View the source

Three steps

No account to create on our end. You sign in with GitHub, and GitHub is where your data lives, before, during, and after you use OpenStore.

Add OpenStore to your AI

Pick the entry point that matches how you work. All three talk to the same hosted OpenStore endpoint.

Connect to Claude

Claude.ai & Claude Desktop: Settings → Connectors → Add custom connector, then paste the MCP URL. Sign in with GitHub when prompted.

https://mcp.openstore.sh/mcp

Claude Code:

claude plugin marketplace add intreaction/openstore

claude plugin install openstore@openstore

Then run /mcp inside Claude Code to sign in.

Connect to OpenAI

ChatGPT: Settings → Apps → Advanced settings → Developer mode on → Create app, then paste the MCP URL. Sign in with GitHub when prompted.

https://mcp.openstore.sh/mcp

ChatGPT asks for your approval before it runs any write action.

Install via MCP

Any other MCP client — Cursor, VS Code, Windsurf, a custom agent — can connect directly to the same endpoint:

https://mcp.openstore.sh/mcp

It speaks Streamable HTTP with standard OAuth 2.1 (dynamic client registration and PKCE). Add /readonly to the URL for a read-only connection.

Sign in with GitHub

Whichever entry point you used, sign in with GitHub through the OpenStore GitHub App when your AI asks. OpenStore creates a private store repository for you automatically — or, under "Advanced," you can pick an existing repository instead. This page has no buttons that touch GitHub; the sign-in happens inside your AI client.

Talk

Ask it to remember something, correct something, or recall something from months ago. It greps and cats the store to answer, and writes a normal Git commit — visible, diffable, revertable — only after you agree.

How it works

OpenStore sits between your AI client and GitHub for exactly as long as one request takes. It never becomes a third copy of your data.

Bash-like tools

Your AI uses tools it already understands — grep, cat, write — scoped to your repo's text files only.

Direct commits

Every write is one ordinary commit to your branch. No proposals, no approval pages. Undo with git_revert.

Consent in chat

The model shows the change before writing, and your AI client prompts you before running a write tool.

How your data is handled

OpenStore passes requests through to GitHub. It processes content and credentials in memory without saving them in application storage.

Your client holds connection credentials and may retain retrieved content. GitHub stores your notes and history. Cloudflare provides the hosted endpoint and may retain network diagnostics separately from the application.

No application database of notes or user credentials
Worker invocation logs and traces disabled
Source and deployment configuration available for inspection

Read our Privacy Policy for retention, provider processing, and deletion limits.

Take it with you

It is just Markdown in your repo. If you stop using OpenStore, or any AI at all, you are left holding a folder of plain files with full Git history — readable, searchable, and useful on their own, in any editor, forever.

Uninstall the plugin or revoke the GitHub App's access whenever you like. Nothing about your data depends on OpenStore continuing to exist.