Skip to content
Oase Developers

What is the Oase MCP?

The Oase MCP is a Model Context Protocol server that lets Claude — or any MCP-capable agent — chat inside an Oase. Give the agent an invite link and it can post into that oase’s group chat, publish posts (opslag) to the oase’s feed, read replies, and even page you and wait for an answer mid-task.

Source: github.com/oase-app/oase-mcp (currently a private repository — non-members will see a 404; for access, write to hello@oase.app).

Why you’d want it

Section titled “Why you’d want it”

  • Status updates where you already are. “I finished the deploy” lands in your group chat, on your phone, not in a terminal you closed.

  • Questions that block until you answer. ask_and_wait posts a question and waits for your reply in the thread — a remote “ask the user” for long-running tasks:

    “Before you deploy, ask me in Oase whether to run migrations, and wait.”

  • A responsive agent in the chat. In listen mode the agent blocks until someone posts, responds, and listens again — every message gets a reply or at least a reaction, with a “typing…” indicator while the agent composes, just like a human participant.

  • Posts on the feed, not just chat. send_post publishes a proper post (opslag) with a title to the oase’s front page — announcements and longer write-ups where they belong, while chat stays chat.

  • Attachments too. The agent can download and decrypt images (viewed inline), voice messages (saved for local transcription) and files.

How it fits Oase

Section titled “How it fits Oase”

The server talks to the production Oase backend exactly like the app does: sign in → join via invite link → fetch the oase key → encrypt → post. Messages are encrypted client-side with the oase’s symmetric AES-256-GCM key (the same per-oase key the app uses, fetched from the KMS via a mainframe-signed proof), so the agent’s messages render normally in the app and the send endpoint never sees plaintext. See Architecture & encryption for the details.

The agent gets its own persistent identity via Promise — the identity provider the Oase app uses — through a one-time browser login. After that it is just another participant: it joins oases from invite links, has a display name (default “Claude”), and can be removed like anyone else.

Where to go next

Section titled “Where to go next”