OmniContext

Official registry AI and agents

Persistent cross-device memory for Claude: your profile, projects, and resumable handoffs.

What can you do with OmniContext?

  • Knows you. A profile (role, preferences, tools, facts) shared with every session. Claude adds to it when you tell it something lasting (remember).
  • Knows your projects. Name them once, give them nicknames, and "my game project", "the website" or "that bot" resolve to the right one in any session. Each project keeps notes, its repo, and its folder on each device.
  • Resumes across devices. /omnicontext:handoff saves a self-contained summary and next steps. On another machine, /omnicontext:resume picks it up and opens the project's folder on that device.
  • Syncs without a cloud service. Your memory is a folder of plain Markdown and JSON files (~/.omnicontext) synced through a private git repo you own. Nothing goes to a third-party server.
  • Works everywhere. It's a Claude Code plugin with auto-injected context, an MCP server for Claude Desktop, Cursor, VS Code, Windsurf and Zed, a desktop app for Mac, Windows and Linux, and a CLI.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @aaryanbindage/omnicontext
Claude Code
claude mcp add omnicontext -e 'OMNICONTEXT_HOME=<OMNICONTEXT_HOME>' -- npx -y @aaryanbindage/omnicontext@0.1.2 mcp
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "omnicontext": {
            "command": "npx",
            "args": [
                "-y",
                "@aaryanbindage/omnicontext@0.1.2",
                "mcp"
            ],
            "env": {
                "OMNICONTEXT_HOME": "<OMNICONTEXT_HOME>"
            }
        }
    }
}

Environment variables

  • OMNICONTEXT_HOME Data folder (default ~/.omnicontext)

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. OmniContext
  2. What it does
  3. Install
  4. Sync your devices
  5. MCP tools
  6. Data format
  7. Privacy
  8. Development
  9. License

OmniContext

Persistent, cross-device memory for Claude.

Every Claude session — Claude Code, Claude Desktop, any MCP client, on any of your machines — knows who you are, what you're working on, and where you left off.

Download (Mac · Windows · Linux) · Claude Code plugin · MCP server · Website


You (on your laptop):  continue my game project
Claude:                Resuming Starfall (the Godot space roguelike). Last session on your desktop
                       you finished the enemy state machine; next up is the boss fight timings…

What it does

  • Knows you. A profile (role, preferences, tools, facts) shared with every session. Claude adds to it when you tell it something lasting (remember).
  • Knows your projects. Name them once, give them nicknames, and "my game project", "the website" or "that bot" resolve to the right one in any session. Each project keeps notes, its repo, and its folder on each device.
  • Resumes across devices. /omnicontext:handoff saves a self-contained summary and next steps. On another machine, /omnicontext:resume picks it up and opens the project's folder on that device.
  • Syncs without a cloud service. Your memory is a folder of plain Markdown and JSON files (~/.omnicontext) synced through a private git repo you own. Nothing goes to a third-party server.
  • Works everywhere. It's a Claude Code plugin with auto-injected context, an MCP server for Claude Desktop, Cursor, VS Code, Windsurf and Zed, a desktop app for Mac, Windows and Linux, and a CLI.

Install

Desktop app (Mac · Windows · Linux)

Download from Releases:

OSFile
WindowsOmniContext-Setup-x.y.z.exe (installer) or …-Windows-x64.zip (portable)
macOS…-macOS-arm64.dmg (Apple Silicon) / …-macOS-x64.dmg (Intel)
Linux…-Linux-x86_64.AppImage or …-Linux-amd64.deb

The app lets you edit your profile, projects and handoffs, set up sync, and connect Claude Code and Claude Desktop with one click. It stays in the tray and syncs in the background.

macOS builds aren't notarized yet. If macOS says the app is damaged, run xattr -cr /Applications/OmniContext.app.

Claude Code plugin
/plugin marketplace add aaryanbindage/omnicontext
/plugin install omnicontext@omnicontext

Requires Node.js 18+. You get:

SessionStart hookinjects your profile, project index, the current project, and open handoffs
SessionEnd hooksyncs your memory to your other devices
/omnicontext:handoff [title]save the current work so it can be resumed anywhere
/omnicontext:resume [project]continue the latest (or a named) handoff
/omnicontext:remember <fact>remember something about you or a project
/omnicontext:project [name aka nickname]register this folder as a project
/omnicontext:syncsync now
MCP tools + skillClaude resolves "my X project", saves notes and handoffs
Claude Desktop & other MCP clients

One click: download omnicontext.mcpb from Releases and open it with Claude Desktop. You can also use the desktop app (Connect Claude → Install) or run npx @aaryanbindage/omnicontext install claude-desktop.

Manually (Claude Desktop, Cursor, Windsurf, VS Code, Zed, Cline and others):

{
  "mcpServers": {
    "omnicontext": { "command": "npx", "args": ["-y", "@aaryanbindage/omnicontext", "mcp"] }
  }
}
CLI
npm i -g @aaryanbindage/omnicontext
omnicontext project add "Starfall" --alias "my game" --tag godot --desc "2D space roguelike" --path .
omnicontext resolve "my game project"
omnicontext remember "Prefers TypeScript and short answers"
omnicontext sync --github          # one-time: create a private repo and sync

Sync your devices

On your first device:

omnicontext sync --github                  # needs the GitHub CLI (gh auth login); creates <you>/omnicontext-data (private)
# or
omnicontext sync --remote <any git url you own>

On every other device, connect the same repo:

omnicontext sync --remote https://github.com/<you>/omnicontext-data.git
omnicontext device "MacBook"               # optional: a friendly device name

You can do the same from the desktop app's Sync & devices tab. After that, sync runs on its own: at the start and end of each Claude Code session, a few seconds after the MCP server makes a change, and every few minutes while the desktop app is open. Each record is its own file, so two devices rarely conflict. When they do, the local version wins, and git history keeps everything.

MCP tools

ToolPurpose
get_contextFull briefing: profile, projects, open handoffs (for clients without hooks)
get_profile / update_profile / rememberRead and update what Claude knows about you
list_projects / get_project / upsert_project / add_project_noteManage projects, nicknames, per-device folders, notes
resolve_project"my game project" → the matching project, ranked
save_handoff / list_handoffs / resume_handoff / complete_handoffCross-device resume
search_memorySearch the profile, notes, and handoffs
sync_nowPush and pull with your other devices

It also provides the prompts resume and handoff.

Data format

~/.omnicontext/
  profile.md               # you — edit freely
  projects/starfall.json   # name, aliases, tags, description, repo, paths per device, notes
  handoffs/<id>.json       # title, summary, next steps, files, device, status
  local.json               # this device only (name, sync prefs) — not synced

Set OMNICONTEXT_HOME to use a different folder. You can also put the folder in Dropbox, iCloud or OneDrive instead of using git sync.

Privacy

Everything stays on your machines and in the git remote you choose. OmniContext has no server, no telemetry, and no account. Don't store secrets in it. The instructions it gives Claude say the same.

Development

npm install
npm test
npm run build          # bundles dist/omnicontext.mjs (used by the plugin, the app, and npm)
cd app && npm install && npm start     # run the desktop app

Releases: push a v* tag. GitHub Actions builds the Windows, macOS and Linux apps and the .mcpb bundle, and publishes to npm.

License

MIT © aaryanbindage

Frequently asked questions

What is OmniContext?

Persistent cross-device memory for Claude: your profile, projects, and resumable handoffs.

How do I install OmniContext?

It runs on your machine. In Claude Code: claude mcp add omnicontext -e 'OMNICONTEXT_HOME=<OMNICONTEXT_HOME>' -- npx -y @aaryanbindage/omnicontext@0.1.2 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does OmniContext need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is OmniContext open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains OmniContext?

It is published by aaryanbindage. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.