Skip to main content
Slashy runs an MCP server, so any AI tool that speaks MCP can use your email, calendar, and research tools directly. No API keys, just a Google login.

​
Quick setup

This one command adds Slashy to every AI tool on your machine:
It lists the tools it finds, you tick the ones you want, and it writes the config for you. Works with Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf, Zed, Gemini CLI and more. Then open your tool and sign in with Google when it sends you to the browser.
Setting it up by hand instead? Every client uses the same server URL: https://slashy.ctrlcenter.ai/mcp

​
Set up your client

​
Claude Code

Run this in your terminal:
Claude Code opens your browser. Sign in with Google and click Allow. Full guide with screenshots

​
Claude app & web

Open Settings → Connectors in Claude Desktop, or go to claude.ai/settings/connectors.
Click Add custom connector and fill in:
  • Name: Slashy
  • URL: https://slashy.ctrlcenter.ai/mcp
Leave the OAuth client ID and secret blank, then click Add. Sign in with Google and click Allow.
On Team and Enterprise plans an Owner adds the connector once at Admin settings → Connectors, then each member connects their own Slashy account.
Claude Desktop guide · claude.ai guide

​
Cursor

Install in Cursor Clicking Install opens Cursor and adds the server for you. To do it by hand, put this in mcp.json:
Quit Cursor with Cmd+Q and reopen it, then sign in with Google and click Allow. Full guide with screenshots

​
Codex CLI

Add this to ~/.codex/config.toml:
Run codex. It opens your browser on first launch. Sign in with Google and click Allow. Full guide with screenshots

​
Notion

Open your custom agent’s Tools / Connectors settings and choose Add custom connector:
  • Name: Slashy
  • URL: https://slashy.ctrlcenter.ai/mcp
Save it, then sign in with Google and click Allow. Full guide

​
Any other client

MCP is an open standard, so a client Slashy has not documented usually still works. Most of them take a config file in this shape:
If your client asks for the details in a form instead, give it the server URL above, choose HTTP transport and OAuth, and leave any client ID and secret fields blank. Slashy registers your client automatically during the first login.

​
Check it worked

Start a new chat and ask “What Slashy tools are available?”. The client lists tools such as send_email, list_calendar_events, and research_contact. If nothing appears, see Troubleshooting.
Install the Slashy skill so your client reaches for Slashy on its own, instead of you writing “use Slashy” in every prompt.

​
What you can do once connected

See Using Slashy MCP for prompts to copy.

​
Security

Slashy uses OAuth 2.1 with PKCE. You sign in through your browser once and your client stores a short-lived access token that refreshes automatically in the background. Your config file holds only the server URL, never a secret.
Tools are scoped to your Slashy account and respect the same permissions as Slashy itself. A client can only do what you can do.
Revoke access at any time from your Slashy account settings. The client is disconnected immediately and its token stops working.

​
Go deeper

Overview & prerequisites

What Slashy MCP is and what you need before setup.

Using Slashy MCP

Ready-made prompts for email, calendar, and research.

Slashy skills

Turn Slashy workflows into one-word triggers.

Troubleshooting

Fixes for OAuth, missing tools, and wrong accounts.