Busabase for Slashy

Connect Slashy to Busabase

Slashy is an AI-native email and calendar client (Gmail, Google Workspace, Outlook) whose agent drafts replies, triages the inbox and acts on your behalf, and can be reached from iMessage and Slack.

Busabase MCP server

https://busabase.com/api/mcp

Read the Slashy documentation

Busabase

MCP connector

Set it up

Hosted chat has no shell and no file system, so a connector is the way in.

Add the server

Point your chat client at the Busabase MCP endpoint.

Sign in

Complete OAuth in the browser — no client id or secret to create.

Pick the smallest permission

changeRequest lets the agent propose but never merge.

Verify

Ask the agent to call auth_verify before it does any work.

Step by step

This host has no shell, so a connector is the only way in.

At a glance

Vendor: Karvix Inc. (doing business as Slashy)
How it connects: MCP + OAuth · MCP + API key
Transport: Unknown
Authentication: OAuth (dynamic registration)
Config file: Settings (Cmd+,) > Integrations > Add MCP

In Slashy press Cmd+, to open Settings and go to Integrations.
Click Add MCP (or search for a service not in the catalog and choose Add external MCP).
Paste https://busabase.com/api/mcp as the server URL. Leave the auth dropdown on Automatic so Slashy starts the OAuth sign-in (Busabase supports dynamic client registration; scope mcp). If you prefer an API key, choose Bearer token and paste a key created in Busabase Settings > API Keys (smallest permission, finite expiry).
Approve the Busabase consent screen. The server card should show a tool count; you can switch individual tools off.
Ask the Slashy agent to call auth_verify.

See the vendor doc: https://help.slashy.com/how-to-guides/connect-mcp-servers

Known gotchas

Slashy has a 7-day free trial that requires a card; sign-in is described as available 'after you've been granted access', so access may be gated. Slashy also publishes its OWN MCP server (https://slashy.ctrlcenter.ai/mcp, OAuth 2.1 + PKCE) so Claude/Cursor/Codex can use Slashy; that is the opposite direction from this row. The vendor doc does not name the MCP transport it supports for custom URLs. Slashy has no shell, so the Skill path does not apply.

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	Slashy	Claude Code	Cursor
Type	Web chat	Terminal agents	AI editors
Recommended path	MCP connector	Agent Skill	Agent Skill
How it connects	MCP + OAuth · MCP + API key	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Unknown	Streamable HTTP	Streamable HTTP
Authentication	OAuth (dynamic registration)	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Oct 21, 2026

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.

Browse every agent

Busabase MCP server

https://busabase.com/api/mcp