โ† BLOG
ยท Arc0 team

Connect Claude to Gmail, Slack, and GitHub with one MCP URL

Step by step: connect Claude to Gmail, Slack, and GitHub through one remote MCP URL in Claude, Claude Code, ChatGPT, and Cursor, with limits per assistant.

Claude can already read your inbox, provided you're on the right plan, in the right app, with the right connector switched on. Then you open ChatGPT or Cursor for a quick job, and the connectors you set up in Claude didn't come along. Each client wants its own setup.

This guide shows how to connect Claude to Gmail, Slack, and GitHub two ways: with Claude's built-in connectors, one app at a time, and with a single remote MCP URL that carries all of them into Claude on the web, Claude Desktop, Claude Code, ChatGPT, and Cursor. Short version: add one URL, https://api.arc0.ai/mcp, as a custom connector and sign in once. By the end you'll have the apps connected, limits set for each assistant, and a test prompt per app that proves it works.

What Claude's built-in connectors already do (and where they stop)

Check the built-ins first, because for some readers they're enough. Claude's connectors live under Customize > Connectors (in Claude Desktop, Customize in the sidebar, then Connectors), and each one has per-tool permissions: Always allow, Needs approval, or Blocked.

ConnectorPlansWhat it doesWhere it stops
GmailPro, Max, Ultra, Team, EnterpriseSearches and reads mail; Anthropic's support page adds draft, send, reply, and forward, with approval before each send by defaultAnthropic's pages disagree on send: the Gmail connector page says Claude can't send, so check your connector's tools
SlackTeam and Enterprise, and Pro and Max per Anthropic's January 2026 updateSearches channels, direct messages, and filesSearch only, and the Claude in Slack app must be installed first
GitHubEvery plan, including FreeReads file names, file contents, and branchesCan't see commit history, pull requests, or issues; Anthropic points you to Claude Code for edits and pull requests

On Team and Enterprise, none of these appear until an Owner switches them on in Organization settings > Connectors; members then connect their own accounts.

If you've connected GitHub, asked Claude about an open pull request, and it couldn't see the pull request, nothing is broken. The integration did exactly what its page says it does.

The built-ins are good at one app in one client. The gaps show up when you switch clients. A connector you add on claude.ai follows you into Claude Code when you're logged in with the same account, but not into ChatGPT or Cursor, and each app brings its own plan rules.

Why one MCP URL instead of three

MCP (Model Context Protocol) is the standard way an assistant talks to outside tools. A remote MCP server is just a URL your assistant signs into. The sign-in usually uses OAuth, which is the consent screen where you approve what an app may access.

Claude calls a server you add yourself a custom connector.

Arc0, which publishes this blog, is one of those URLs, and it's the worked example from here on. Your Arc0 URL, https://api.arc0.ai/mcp, is bound to you: sign in once and it reaches Gmail, Slack, GitHub, and the rest of a catalog of 1,484 apps, from any client that speaks remote MCP. You get it free on Arc0 for individuals.

Diagram: any MCP client, such as Claude, ChatGPT, or Cursor, signs in to one Arc0 MCP URL bound to you, which reaches your three apps, Gmail, Slack, and GitHub, with apps chosen per assistant

The assistant doesn't drag every tool from every app into its context, either. It searches a short list of what you've authorized and calls the one it needs. And on Claude's Free plan, which allows one custom connector, a single URL for every app fits that limit exactly.

Our opinion: set permissions once, in one place, not again in every client you open.

Step 1: get your Arc0 MCP URL and connect the three apps

Whichever MCP server you pick, the order is the same: your account first, your apps second, your client last. On Arc0, the account is the free Personal plan.

  1. Sign up from Get started at arc0.ai/signup.
  2. Open Personal Arc0 from the user menu. It has no organization and no billing, and the plan reads Free.
  3. Go to My apps and choose Add an app.
  4. Add Gmail, Slack, and GitHub. Each one sends you to the provider's own sign-in page; calls run on Arc0's servers, and your credentials never reach the model.
  5. Copy your personal MCP URL from the top of the page.

The Personal docs cover the same screens.

  • Gmail lists and reads messages, reads drafts, and creates drafts. There's no send: a draft notifies nobody, which is the right default for an inbox an assistant is still learning. Keep Claude's built-in Gmail if you need sending, once you've checked it lists a send tool (see the table above).
  • Slack lists channels, reads channel history, looks up a user by email, posts, replies in threads, adds reactions, and deletes the bot's own messages. It reaches only channels the bot has joined. Keep the built-in if search across DMs and files in claude.ai is all you need.
  • GitHub searches and lists repositories, reads your profile and public repos, and creates issues, with no labels, pull requests, or merges. Keep Claude's GitHub integration for reading code, and Claude Code for pull requests.

One plain warning on GitHub: its sign-in asks for the repo scope, which is broad repository access, not a read-only grant. Decide now which of your assistants deserve that; Step 3 shows how to keep it from the rest.

Step 2: add the URL to Claude

Any remote MCP server goes into Claude the same way, through the custom connector screen, and that screen works on every Claude plan, Free included. The Claude setup page and the MCP client docs have the Arc0 specifics.

Claude on the web and Claude Desktop

  1. Open Customize > Connectors (in Desktop, Customize in the sidebar, then Connectors).
  2. Choose Add, then Add custom connector.
  3. Name it Arc0, paste https://api.arc0.ai/mcp as the server URL, and choose Continue.
  4. Review the authentication settings. Sign-in can be Sign in now, Sign in when needed, or No sign-in, and the OAuth client can be Claude's published identity, automatic registration, or your own; keep whatever Claude marks Detected.
  5. Choose Add, then Connect, and sign in to Arc0. Adding the URL alone doesn't finish setup: it works once that sign-in completes.
  6. In a chat, select +, then Connectors, and switch Arc0 on.

On Team and Enterprise, an Owner adds it under Organization settings > Connectors > Add > Custom (type Web), and members then find it under Customize > Connectors and choose Connect.

Get the authentication settings right the first time. Claude won't let you edit them later, so a change means removing the connector and adding it again. Arc0's Personal page says Settings > Connectors; Anthropic's docs say Customize > Connectors, so use that if your menu differs.

Claude Code

Claude Code adds remote servers from the terminal. One command does it:

claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp

The --scope user part matters. Claude Code's default scope is local, which ties the server to the project folder you ran the command in, so Arc0 would vanish the moment you cd somewhere else.

  1. Run /mcp inside Claude Code, select arc0, and choose Authenticate.
  2. Finish the sign-in in your browser. Until you do, claude mcp list shows ! Needs authentication, which is expected, not a fault.
  3. Confirm with claude mcp get arc0.

Added Arc0 on claude.ai already? With the same account it's in /mcp already, so skip the second copy. If an arc0 server exists from an earlier try, check its URL before you replace it. Anthropic's Claude Code MCP docs cover the rest of the flags.

ChatGPT and Cursor (one line each)

ChatGPT (web only): open Plugins, select the plus button, then Add custom MCP server; name it Arc0, paste the URL, choose OAuth (and dynamic client registration if asked), acknowledge the risk, and select Create as a plugin. As of November 2026, OpenAI's developer mode help article lists full custom MCP support on Business and Enterprise/Edu, while Pro connects custom servers with read and fetch permissions only. Details are on the ChatGPT setup page.

Cursor: add an entry to ~/.cursor/mcp.json (or .cursor/mcp.json for a single project), then enable it under Customize in the sidebar; Cursor runs the OAuth sign-in itself. The entry below is built from Cursor's documented format, since Arc0's Cursor page doesn't show one:

{
  "mcpServers": {
    "arc0": { "url": "https://api.arc0.ai/mcp" }
  }
}

The Cursor setup page has the Arc0 side, and MCP client setup lists the other clients.

Step 3: decide what each assistant may do

Claude's built-ins set permissions per tool, inside Claude. In Arc0 Personal you set two things per assistant, in whichever client it runs. The first is which apps it can use. The second is what happens before it deletes anything.

  1. Give the assistant its first task. It then appears under My agents.
  2. On its card, select Choose apps under "Apps it can use" and leave only what it needs.
  3. Under "Before it deletes anything", pick Ask me, Allow, or Block. Ask me holds the call until you approve it.
  4. Open Activity to see every call, filtered by agent and app, with tabs for allowed calls and held or blocked ones.

There's no per-assistant read-only switch: for each assistant, an app is in or out. If you want an assistant that only reads Gmail, it helps that Arc0's Gmail has one write, Create draft, and a draft notifies nobody. In a project, each app's Actions tab can switch actions off, but that switch is for everyone: an action you turn off there disappears from every agent, as the scopes and actions docs explain. Check that the switch shows up in your account first; the docs describe it for projects, not Personal.

Ask me covers destructive actions only. Among these apps, that means Slack deleting the bot's own message; it doesn't hold posts or drafts. You approve in the Arc0 dashboard, and as of November 2026 Arc0 sends no email or push notification for approvals; a request nobody approves expires after 24 hours. The agent can't approve its own request, however politely it asks. The approvals docs have the details.

Worried it'll post in #general as you? Slack actions run through Arc0's bot, which can post only in channels it has joined. An assistant gets Slack's reads and writes together, so leave Slack off any assistant you don't want posting, and watch Activity for the ones you keep it on. Teams running an Arc0 project get a finer rule: a policy such as slack:write~ask holds Slack writes (posts, thread replies, and reactions) for approval.

Our picks: give Claude Code GitHub and nothing else, since what it needs from Arc0 is your repository list and issues, not your inbox. Give your chat assistant Gmail, and save Slack for the assistant you'd trust to post in front of your colleagues.

Step 4: test one prompt per app

Test a read first, check Activity for the receipt, and only then try a write. Writes go somewhere nobody is watching: a sandbox channel is cheaper than an apology in #general.

  • Gmail, read: "Summarize the unread emails from my accountant this week." Write: "Draft a reply to the latest one." It lands in Drafts and nobody is notified.
  • Slack, read: "Show the latest messages in #project-updates," in a channel the bot has joined. If a reply you expected is missing, look in the thread: channel history reads don't include thread replies. Write: "Post 'testing' in #bot-sandbox."
  • GitHub, read: "List my repositories." Write: "Create an issue titled 'Arc0 test' in my sandbox repo."

After each one, check that Activity shows the call under the right agent and app.

Troubleshooting

Usually the connector is off, signed out, or signed in as the wrong you. Almost none of these need a reinstall.

  • Connector missing in Claude. On Team and Enterprise, an Owner has to enable it first. For GitHub, Add from GitHub in the + menu only appears after you connect GitHub Integration under Customize > Connectors.
  • Arc0 missing in Claude Code. It was probably added with the default local scope in another folder; add it again with --scope user.
  • ! Needs authentication or a timeout. Run /mcp, select the server, and choose Authenticate; if the browser doesn't open, copy the URL from the terminal. The default startup timeout is 30 seconds, and MCP_TIMEOUT=60000 claude raises it.
  • Claude lost access. A Reconnect button appears on the connector's row; Disconnect then Connect works too. In Claude Code, claude mcp logout arc0 clears stored credentials before you authenticate again.
  • Arc0 says reconnect_required. The app needs a fresh authorization. Reconnecting keeps the same connection, with its identity and settings.
  • Wrong workspace or account. Revoke the agent's authorization in Arc0 MCP, then authorize the right one; changing the URL won't switch identities.
  • Connect link expired. Hosted connect links work once and expire after 10 minutes, so ask the assistant for another. Never paste a password or token into the chat.
  • Slack can't see a channel. Add the bot to it. Disconnecting Arc0 also leaves the shared bot installed until a workspace app manager removes it in Slack.
  • Revoking everything. Revoking in Arc0 blocks further use, but remove the grant in your Google, Slack, or GitHub settings too.

The end-user MCP docs list every connection state.

Add more apps from the same URL

Adding another app later is the same move as Step 1, My apps then Add an app, and no client has to be told. If you've narrowed an assistant with Choose apps, add the new one to its list there. Browse the app catalog to see which of your tools are in it.

So which route is yours? The built-in connectors are the better fit if you live in one client and want Claude to read code. The same goes for sending email, once your connector shows a send tool. GitHub's costs nothing on any plan. If you use more than one client, or more apps than these, a single Arc0 URL is the simpler setup. You connect each app once, choose each assistant's apps once, and read every call in a 7-day audit log.

To start, get your free personal MCP URL from Arc0 for individuals, connect Gmail, and add the URL to your client with the MCP client setup pages. Your first read takes one prompt.

Get started

One plug. Every app. Any agent.

Your users connect their apps once, under your brand. Your agent, or Claude, ChatGPT and Cursor, acts through one MCP endpoint, with every action on the record.