Olympus MCP server
Commit Nov 16, 2026Olympus provides a privacy-first local memory layer that allows AI clients to access your personal files, emails, and messages through policy-gated access.
Also known as jamiezigelbaum/Olympus
- Stars
- 18
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 16, 2026
- License
- MIT
What is Olympus MCP?
Olympus olympus provides a privacy-first local memory layer that allows AI clients to access your personal files, emails, and messages through policy-gated access.
Summary generated from the project's README
About Olympus MCP server
Accessing personal data from within AI clients like ChatGPT, Claude, or Grok is what Olympus enables through a privacy-first local memory layer. It allows users to connect their emails, files, and messages from sources such as Gmail, Dropbox, and Google Drive while keeping the actual content on their own machine. The system works by indexing data locally on Mac (Apple silicon) or Linux systems running Omarchy or Ubuntu 24.04 LTS, ensuring that sensitive information is never uploaded to a cloud provider.
Users manage data through a policy-gated system that automatically categorizes items as Personal, Private, or Secret. Personal data can be read by frontier models to provide cited answers, while Private data is processed by a local model to generate answers that stay on the computer. Secret data, such as passwords or API keys, is never sent to any model. This setup requires no subscription or account, using a local engine and a relay to pass requests between the AI app and your computer.
What you can do with it
- 1Querying cross-platform communicationsAsk an AI agent to summarize commitments found across different messaging and email services.
- 2Retrieving sensitive information privatelyGet answers from private documents without sending the actual content to a cloud-based AI model.
- 3Protecting credentials from AI modelsEnsure that passwords and recovery codes are never processed or answered by an AI.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
OLYMPUS_BINOLYMPUS_ROOT
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablejamiezigelbaum/olympus is public and reachablegithub.com/jamiezigelbaum/olympus ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/jamiezigelbaum/olympus ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub
⛰️ Olympus
Your machine, your memory. Keep your private things private.
Olympus keeps your email, files and messages on your own computer and decides, item by item, what each AI may see. ChatGPT, Claude, Grok and any app that speaks MCP can use it, while your private things stay private. On a Mac, and on Omarchy and Ubuntu 24.04 LTS Linux. Free and open source.
olympusplugin.ai · Get started · Olympus in ChatGPT · Claude, Grok and other apps · How it works · Sources · Security model · OpenClaw quickstart · Commands
🤖 Installing this as an AI agent for OpenClaw? Stop and read INSTALL_FOR_AGENTS.md before running any command — it is the step-by-step runbook you must follow, including exactly what to tell your operator after each step (your install report must end with the Step 1→2 invitation, never a bare status line). Managed
git:,clawhub:, andnpm-pack:installs intentionally hide their internal package path; use the installedolympusCLI and this packaged runbook rather than searching OpenClaw's managed storage. Setting up Olympus for ChatGPT, Claude or Grok instead? Follow Get started, not this runbook.
Frontier AI models are the smartest, but using them means sending your life to someone else's cloud. Local models keep it home, but they are a step behind, and the best ones need an expensive computer under your desk. Olympus gives you both, on the laptop you already have.
Every email, file and message is judged, one by one, as Personal, Private or Secret: on your own computer by default, or by Venice's private models if you choose a Venice-only setup.
- Personal: ChatGPT, Claude or Grok can read the parts that answer your question, and cite them.
- Private: only a model on your computer reads it (or Venice, if you turn it on); your AI app never gets the item itself. In ChatGPT, only you see the answer; other apps get an answer written from it, which can repeat what it says.
- Secret: passwords, recovery codes and keys. Once Olympus recognizes a Secret, it is never sent or answered from.
Labels are automatic and can be wrong.
Everything is stored and searched on your computer: the search index is built there, by a model small enough for a computer with 8 GB of memory. There is no hosted copy of your things, no account and no subscription. Olympus's publisher runs only a relay that passes your AI app's requests to your computer without storing them. Google sign-in happens on your computer, directly with Google. For hard private questions you can reach stronger models: Venice runs private models that, under Venice's own terms, keep nothing you send, and zkAPI, from OpenAnonymity and the Ethereum Foundation, hides who is asking (see Stronger models, privately).
you › "What did I commit to this week, across email and Telegram?"
agent › Three commitments: the tax documents to Maria by Friday
(email, Tue), reviewing the lease amendment (email, Mon),
and the Saturday ride logistics (Telegram, Wed). [3 citations]
Your agent saw a bounded, cited, policy-gated answer. It never saw your mailbox.
Get started
You need a Mac with Apple silicon (M1 or later) on macOS 13 Ventura or later, or an x86_64 computer running Omarchy or Ubuntu 24.04 LTS. Intel Macs, other Linux distributions and ARM Linux are not supported yet. You do not need OpenClaw, Tailscale, an API key or a new account.
1. Install Olympus on your computer. On a Mac, open Terminal and run:
curl -fsSL https://olympusplugin.ai/install.sh | sh
On Omarchy, first install the tools Olympus uses to read scans, photos and voice notes, then run the Linux installer:
sudo pacman -S --needed tesseract tesseract-data-eng poppler libvips libheif ffmpeg
curl -fsSL https://olympusplugin.ai/install-linux.sh | sh
On Ubuntu 24.04 LTS, install the prerequisites and run the Linux installer:
sudo apt install curl ca-certificates tar unzip coreutils findutils gawk grep diffutils procps util-linux systemd python3 tesseract-ocr tesseract-ocr-eng poppler-utils libvips-tools libheif1 ffmpeg
curl -fsSL https://olympusplugin.ai/install-linux.sh | sh
Each installer installs Olympus for your user only (the installer itself needs no
administrator password; the package installation lines above do),
checks every download against a pinned SHA-256 before using it, keeps Olympus
running in the background (a LaunchAgent on a Mac, a systemd user service on
Linux), adds the olympus command, and waits until the engine proves it is
running. On Omarchy it also adds Olympus to the app launcher. Then Olympus
downloads its built-in models once. Running it again updates or repairs the
install; a failed update puts the previous version back. Details, folders and
uninstall: https://olympusplugin.ai/install/.
2. Connect your AI. Each app has a short guide: ChatGPT · Claude · Grok and Grok Bot · Dots · Claude Code · Codex · OpenClaw · Hermes · any MCP app. In ChatGPT, Claude and Grok you add Olympus's address as a connector (in ChatGPT, in Developer mode until Olympus is listed in its directory), then approve it with one click on a page Olympus opens on your own computer: there is no pairing code and no account to create. Grok Bot then uses the Grok connection. Apps on your computer, such as Claude Code, Codex and Hermes, connect with one command.
3. Connect your sources and ask. Open the dashboard (in ChatGPT, ask
"Show my Olympus dashboard"; on your computer, run olympus dashboard),
connect Dropbox, Gmail or Google Drive, pick folders, and ask the way you
normally would.
Olympus for ChatGPT
In ChatGPT, Olympus is a plugin. The Olympus engine runs on your computer and keeps your index there; ChatGPT asks it questions through one secure connection that you approve on that computer.
1. Add Olympus in ChatGPT
Install Olympus on your computer first (Get started).
Olympus is on its way to ChatGPT's app directory. Until it is listed, add it
yourself: in ChatGPT, open Plugins, choose +, then Add custom MCP
server. Name it Olympus, choose OAuth, and paste
https://mcp.olympusplugin.ai/mcp as the URL. If you don't see Add custom MCP
server, turn on Developer mode in Settings first. OpenAI decides
which accounts have Developer mode; in a work or school workspace, an admin
may need to allow it. Step by step:
https://olympusplugin.ai/install/chatgpt/. On Omarchy,
ChatGPT may still say Olympus needs a Mac; it works on Omarchy too.
2. Approve ChatGPT on your computer
The first time ChatGPT connects to Olympus, an Olympus page opens in your
computer's browser asking Connect ChatGPT to Olympus? Click Connect. (If a
page saying Approve ChatGPT on your Mac comes first, click Continue on
this Mac; the page says Mac on Omarchy too.) Clicking Connect on your own
computer is how Olympus knows the computer is yours: there is no code to copy and no account to create. To check on it later, run olympus engine status in a terminal.
3. Connect Dropbox and choose folders
Open the Olympus dashboard in ChatGPT's sidebar (or ask "Show my Olympus dashboard"). Choose Connect next to Dropbox and sign in with your own Dropbox account; the sign-in link works once, for 10 minutes, from any device. Gmail and Google Drive connect the same way, except that you open their sign-in link on the computer where Olympus runs, not on a phone.
Then pick folders. For each folder choose:
- Full: Olympus reads the files and can answer from what they say.
- Names only: Olympus keeps the file names and details such as dates, not what the files say.
- Skip: Olympus leaves the folder alone.
A folder follows its parent's choice unless you change it; Mixed means some folders inside it are set differently. Choose Save and start, and indexing begins on your computer.
4. Tell Olympus what's private
Olympus sorts every item, one by one, into one of three tiers:
- Personal: everyday mail, notes and files. ChatGPT can see the parts that answer your question, and cites them.
- Private: things you keep to yourself, such as health, money or family matters. What they say is never sent to ChatGPT. Olympus answers from them on your computer, in the private answer panel (below).
- Secret: passwords, recovery codes and keys. What Olympus recognizes as a Secret never reaches a model and is never answered from. Recognition looks for common forms (private keys, API keys, labeled passwords) and can miss others.
Olympus decides on your computer. Once its built-in private model is ready, it checks every item it reads before treating it as Personal. Labels are automatic and can be wrong. In the dashboard, Privacy asks "What's private for you?": answer in your own words. Once you do, only the kinds of things you call private are Private: health or family matters you leave out, or say are fine to share, can reach ChatGPT. You can also mark folders, Gmail labels or senders as always Private.
5. Ask
Ask in ChatGPT the way you normally would: "What did Sam say about the lease?" ChatGPT searches Olympus and answers from your Personal items, with citations.
The private answer panel
When some of the items that match your question are Private, a small Olympus panel appears on its own under ChatGPT's reply: Private answer from your computer, marked Not sent to ChatGPT.
- Your computer writes the answer with its built-in private model (Qwen3.5, sized to its memory: 2B under 16 GB, 4B with more) and sends it to the panel sealed, so only the panel can open it. It goes around the ChatGPT conversation, not through it, and the Olympus relay cannot read it.
- On an Apple silicon Mac it usually arrives within a minute; on Omarchy it depends on the computer's processor and can take a few minutes. Ask for "all the details" and Olympus reads the whole documents instead; that can take a few minutes.
- Sources (closed at first) lists the items the answer used. Click one to open it on your computer, or in Dropbox on the web if it is not on this computer (ChatGPT opens that web link for you, so it sees the address).
- Hide folds the answer away and Show brings it back. An answer expires after 10 minutes; ask again for a new one.
- Ask follow-up questions in the chat as usual; each private answer appears in a new panel.
Your computer needs to be awake and online. The panel runs inside ChatGPT's page, so it relies on the panel code ChatGPT loads; the design states that limit plainly.
What ChatGPT can and can't see
ChatGPT can see:
- The parts of your Personal items that answer a question: excerpts, titles, dates and links.
- File names, including the names of some Private items. A file's name can be Personal while what it says is Private, so its name may show up in ChatGPT; its contents never do.
- That some items matching a question are Private: ChatGPT's model learns just that, with no titles and no content.
- Status: which sources are connected, how far indexing has got, and what needs you. The folder picker shows your folder names inside ChatGPT so you can choose; they pass through ChatGPT to reach the picker, but ChatGPT's model is not given them.
ChatGPT can't see:
- What your Private items say, or the private answers made from them.
- Secret items Olympus recognizes.
- Folders you skip, or what the files in Names-only folders say.
- API keys or passwords: you never enter one in ChatGPT. Optional extras such as a Venice account are set up on your computer.
The relay at mcp.olympusplugin.ai passes ChatGPT's requests to your computer. It
stores and logs no questions, answers or tokens, but like any HTTPS service
it handles them in transit. Full details: the
ChatGPT design and the
trust model.
Claude, Grok and other apps
Claude (web, desktop and phone) and Grok connect through the same Olympus relay as ChatGPT, with one click to approve on your computer, and Grok Bot uses the Grok connection; apps on your computer, such as Claude Code, Codex and Hermes, connect there directly. Guides: https://olympusplugin.ai/install/.
They search what is Personal, with citations, like ChatGPT. They never get
your Private items themselves or the Secrets Olympus recognizes. For Private
items they get at most an answer that the private model on your computer (or
Venice, if you set it up) writes from them, checked for secrets, with each
item's title, path, source and author. That answer can repeat what the items
say. ChatGPT is stricter: it gets no answer from Private items
at all, and shows one only in its private answer panel. When an agent is not
given an answer, Olympus records the question and the model built into
Olympus answers it on your computer; the agent is told only that the answer is
in Olympus on your computer, with a link (olympus://open/private/ and a
random identifier) that opens it there. The answer waits in the dashboard's
Inbox (under On this computer),
which Olympus gives no AI app a way to read, until you delete it, and
Needs you counts the
answers you have not read. More: Connect other
agents.
Stronger models, privately
For hard private questions you can reach stronger models without giving yourself away. Both are off until you turn them on.
- Venice runs private models that, under Venice's own terms, keep nothing you send. Add your Venice key under Keys, on your computer. In Ask a question, a Venice model reads the passages of your files it needs, and is available only if your privacy settings allow Private items to go to Venice; a key alone does not allow it.
- zkAPI, from OpenAnonymity and the Ethereum Foundation, hides who is asking. It pays anonymously and sends the question over Tor (on unless you turn it off; without Tor, your network address shows): no account, no card, no name, just proof the question is paid for. In Strict mode your computer first rewrites the question into general questions; Standard, by default, takes out names, contact details and account numbers, or sends your words as written if you choose that. What you ask can still identify you. Turn on Anonymous answers under Keys on your computer, then ask from your agent or from Ask a question in the dashboard's Inbox; each question as sent, and its reply, stay in the Inbox on your computer until you delete them or the Inbox removes the oldest when full. Anonymous answers work on a Mac and on Omarchy and Ubuntu 24.04 LTS (x64), once Olympus's network isolation checks pass.
Uninstall
On a Mac, run curl -fsSL https://olympusplugin.ai/uninstall.sh | sh; on
Linux, curl -fsSL https://olympusplugin.ai/uninstall-linux.sh | sh. Both
stop Olympus and remove the app, the runtime and the olympus command, and
keep your settings and data. To delete those too, first run
olympus engine stop and olympus data delete --all. To only stop Olympus
and remove its login item or service, run olympus engine uninstall.
The rest of this README covers how Olympus works and Olympus with OpenClaw, which stays supported and optional.
How it works
Olympus ingests your sources into local, trust-tiered indexes, then lets your frontier agent answer questions across all of them, with sensitive material handled only by lanes you approved: your own local models, privacy-approved private cloud inference, or not at all.
Every item you ingest is judged on its own as Personal, Private, or Secrets (plus Public on installs made before 1.0; internally S0-S5): its names are Personal unless something raises them, and its content is raised to Private or Secrets on evidence. Each tier has its own index and routes only to the model lanes your sovereignty policy allows:
flowchart LR
subgraph sources["Your sources"]
direction TB
SRC1[Gmail · Drive · Dropbox]
SRC2[Telegram · WhatsApp · X]
end
subgraph olympus["Olympus (local)"]
direction TB
ING[Ingest & classify<br/>every item, locally]
IDX[(Trust-tiered<br/>local indexes)]
POL{{Sovereignty policy<br/>your rules, enforced}}
ING --> IDX --> POL
end
subgraph lanes["Model lanes you approved"]
direction TB
CLOUD[Frontier cloud<br/>everyday content]
PRIVATE[Venice<br/>Private content when routed]
LOCAL[Your local models<br/>Private content]
end
AGENT[Your agent<br/>cited, bounded answers]
sources --> ING
POL --> CLOUD & PRIVATE & LOCAL
CLOUD & PRIVATE & LOCAL --> AGENT
Olympus uses Personal (ordinary personal and work content), Private (sensitive material), and Secrets (once recognized, never model input). There is no Public tier on any new install, ChatGPT or OpenClaw, whichever posture you choose: anything that would have been Public is Personal. Installs made before 1.0 keep a Public tier. See the tier mapping for the unchanged storage identifiers.
Four postures, chosen (and changeable) in setup — a config file, not a code fork:
| Preset | Personal content | Private content: health, finance, legal, therapy, family |
|---|---|---|
Local models and private cloud (local-first) |
frontier cloud | approved secure pool with explicit local → Venice Private order |
Local models only (local-only) |
frontier cloud | your own local models only |
Private cloud only (private-cloud-only) |
frontier cloud | Venice Private model (kimi-k3) |
Private meaning search on this computer (no-sensitive) |
frontier cloud | stored and searched by meaning on this computer: its search vectors come from the built-in model and are kept here; no Private agent answer lane |
“Private cloud only” describes Private-data handling: Venice answers Private questions. Search indexing for every tier uses EmbeddingGemma 2, Google's small embedding model, built into Olympus: it downloads once, runs on your computer, needs no account or key, and sends nothing anywhere. On a Mac it also reads pictures, so photos are searchable by what is in them. The embedding choices are built-in local EmbeddingGemma or Venice. Existing Gemini and local-server configurations remain compatible; see the embedding migration guide. Private content never goes to Gemini. Personal questions use OpenClaw's own configured default model.
One question searches every tier. When it finds Private evidence, the private lane your posture approved answers it and your agent receives only the checked, cited answer. Secrets Olympus recognizes are never searched by content: it can tell you where one lives, never what it says.
Some rules are not configurable, by design: secure content never routes to ordinary cloud models, recognized secrets are denied to every lane, and an exhausted policy chain refuses rather than silently downgrading.
Get started with OpenClaw
Using ChatGPT? See Olympus for ChatGPT instead; none of this section is needed.
You need OpenClaw 2026.7.1+ on a Node release OpenClaw itself supports
(>=24.16.0 <25 or >=26.1.0 for OpenClaw 2026.9.5; check
npm view openclaw engines — its installer refuses any other), plus
Bun 1.2+. macOS or Linux.
Paste this into OpenClaw, or another agent with a terminal:
Install Olympus by reading https://raw.githubusercontent.com/jamiezigelbaum/Olympus/main/INSTALL_FOR_AGENTS.md and following it step by step. Walk me through setup and ask me about my data and privacy preferences.
Your agent downloads the designated pilot package, checks it automatically, and guides you through setup. You do not need to download files, find a checksum receipt, or have a GitHub account. The agent checks the SHA-256 and byte count against the designated candidate and GitHub's release metadata.
Olympus is also published on ClawHub (https://clawhub.ai/plugins/olympus,
from 1.3.4), so openclaw plugins install clawhub:olympus installs the same
release bytes. ClawHub can trail the newest GitHub release by a little. The
agent install above and release qualification use the managed npm-pack: path — see
docs/V0_4_RELEASE.md. A Git checkout or rebuilt package
does not qualify the supplied candidate.
--accept-capabilities is required by OpenClaw 2026.8.1+: an agent-driven
install is non-TTY, and without the flag the host exits 1 asking for capability
consent it cannot prompt for. Omit the flag on 2026.7.1, which does not
define it.
The agent checks prerequisites, installs the plugin, talks through what is private for you (you save it later in the dashboard's Privacy section), asks for your privacy posture and your approval of the private classifier, verifies the worker, restarts the gateway, and hands you the dashboard. You paste your model keys into its Models section yourself; the agent never collects them. That completes base installation. Then you can choose a source in the dashboard or leave Olympus ready for later; no source is selected for you. Once your chosen source is ready, the agent checks a first answer and its citations.
Prefer to drive it yourself? Follow docs/QUICKSTART.md, starting with the automatic download and existing-install checks. Its install command for a clean machine is:
openclaw plugins install npm-pack:/absolute/path/to/olympus-1.4.4.tgz --force --accept-capabilities
# On OpenClaw 2026.7.1, omit both flags for a clean install.
Olympus MCP questions
Do I need an account or subscription to use Olympus?
No, there is no account to create and no subscription required; everything is stored and searched on your own computer.