GitHub Copilot

How to use Slack with GitHub Copilot

You want Slack inside GitHub Copilot so it can triage a busy Slack workspace, coordinate people in the right channels, summarize a decision thread, and publish an approved team update — without you copy-pasting between tabs. Here is the whole setup, once.

Create your Slack gateway

The gateway is the thing GitHub Copilot connects to, and it is where you decide which Slack tools an agent may use. You create it once and every client reuses it.

  1. Create an Arcade account

    Sign up and open the dashboard. The free tier is enough to follow this through.

  2. Create an MCP Gateway and select your Slack tools

    In the dashboard, create a gateway and pick the Slack tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.

  3. Copy your gateway URL

    Every client below needs it.

    https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>

Connect the gateway to GitHub Copilot

Heads up

JetBrains IDEs do not support remote MCP servers with Dynamic Client Registration — configure the gateway as “Arcade Headers” in the dashboard first. Setup also differs on Visual Studio, Eclipse and Xcode; check the docs for yours.

  1. In VS Code

    Copilot picks up MCP servers configured in VS Code automatically, so follow the VS Code steps and you are done.

  2. In JetBrains IDEs

    Copilot icon → Open Chat → Agent mode → tools icon → “+ Add More Tools…”, which opens mcp.json.

  3. Add the gateway with Arcade Headers

    {
      "servers": {
        "mcp-arcade": {
          "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>",
          "requestInit": {
            "headers": {
              "Authorization": "Bearer {arcade_api_key}",
              "Arcade-User-ID": "{arcade_user_id}"
            }
          }
        }
      }
    }

  4. Try it out

    Open Copilot Chat in Agent mode and ask it to use one of your Slack tools. The first time it calls a Slack tool, Arcade replies with an authorization link. Open it, sign in to Slack and approve access, then ask again. You do this once per account.

Get started with these Slack prompts

GitHub Copilot can now act on your Slack account. Copy a prompt and paste it in.

triage a busy Slack workspace

Search my accessible Slack messages from the last three days for customer questions, incidents, and requests that need follow-up. Group the results by topic, include links and authors, and list anything that still needs a reply; do not send messages.

coordinate people in the right channels

Find the Slack profiles for the people named in this request, identify the relevant channel, and invite anyone who is not already a member. Before inviting or sending anything, show me the proposed members, channel, and message for approval.

summarize a decision thread

Find the Slack thread about the project decision I describe, read the parent and replies, and return the decision, unresolved questions, named owners, and links to the relevant messages. Do not edit or reply to the thread.

publish an approved team update

Draft a concise Slack update from the facts I provide, targeting the channel or thread I name. Show me the exact draft and destination for approval, then send it only after I approve; return the posted message link.

A mistaken invite or message can reach the wrong people. Pair Slack with Contextual Access policies to require approval before invites or messages, and limit the conversations an agent can access.

Ready to actually ship your agent?

Free to start. Ready for enterprise when you are.