Skills

What plugs into the Rush surface.

Mail. Calendar. Repos. Chat. Files. And any MCP server you trust. This page only lists surfaces we can point to in the product or the public release log.

Accounts you already useMCP-based extension layerProof linked on every claim
01Connected accounts

GitHub

Read repositories, review pull requests, and file issues with your own identity — not a shared service account.

Shipped in Alpha 19.

See the release note

Google Workspace

Gmail, Calendar, and related Google surfaces can be connected when the workflow calls for mail, scheduling, or sheet-backed work.

OAuth moved into the system browser in Alpha 19.

See the release note

Microsoft 365

Outlook, Calendar, and Teams light up through Microsoft sign-in, so agents can work on the other side of the fence too.

Microsoft sign-in landed in Alpha 20; Outlook and Calendar followed in Alpha 23.

See the release note

Slack

Search channel context, route work through connected channels, and keep the same memory model across Slack conversations.

Slack-connected flows are documented across Alpha 19 and Alpha 30.

See the release note

Files and docs

Box, Dropbox, Google Drive, and Lark appear as connectable surfaces when agents need files instead of another chat transcript.

Connection tiles and Drive scope controls shipped in Alpha 31.

See the release note
02The connection layer

MCP-first

Rush does not stop at the built-ins.

Connections are MCP servers. That means a private wiki, project tracker, or internal tool can become part of an agent workflow without waiting for Rush to hard-code it.

  • Confluence for internal knowledge
  • Jira for sprint and ticket context
  • GitHub for code and pull requests
  • Slack for channel history and follow-up

MCP registry

Rush can browse public MCP servers and add them as connections, so the surface is not capped at built-in tools.

Open docs

Custom servers

If a server is not in the registry yet, Rush supports custom MCP runners through npx, uvx, bunx, and docker.

Read the builder docs

Per-agent access

Connections are not all-or-nothing. You can keep a research source attached to one agent and off-limits to another.

See the product surface
03Where to go next

For operators

Install the runtime first.

The fastest way to feel the surface is still the local app. Connect one account. Run one real workflow.

Download Rush

For builders

Bring your own server.

The storefront lives here. The builder path lives on prix.dev and the developer docs.

Open prix.dev docs