Add Slack MCP server authentication to stress test workflow

[Copilot]

The nightly stress test detected that Slack MCP server requires SLACK_BOT_TOKEN and SLACK_TEAM_ID environment variables for authentication.

Changes

Workflow configuration (.github/workflows/nightly-mcp-stress-test.md):

• Added env section to slack MCP server definition with both required secrets
• Follows same pattern as existing GitHub MCP server authentication

slack:
  type: stdio
  container: "mcp/slack"
  env:
    SLACK_BOT_TOKEN: "${{ secrets.SLACK_BOT_TOKEN }}"
    SLACK_TEAM_ID: "${{ secrets.SLACK_TEAM_ID }}"

Note: The .lock.yml file is not included in this PR as it will be regenerated automatically during workflow compilation using gh aw compile.

Prerequisites

Repository secrets SLACK_BOT_TOKEN and SLACK_TEAM_ID must be configured before the stress test can authenticate with Slack. After merging, run gh aw compile nightly-mcp-stress-test to regenerate the compiled workflow.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[mcp-stress-test] Slack MCP Server requires SLACK_BOT_TOKEN authentication</issue_title>
<issue_description># MCP Server Authentication Required: Slack

The nightly stress test detected that the Slack MCP server requires authentication to function properly.

Test Details

• Test Session: stress-test-20260204-180602
• Test Date: 2026-02-04T18:06:02Z
• Server Container: mcp/slack

Required Authentication Token

Environment Variable: SLACK_BOT_TOKEN and SLACK_TEAM_ID

Token Type: Bot User OAuth Token

How to Obtain:

1. Visit: (api.slack.com/redacted)
2. Create a new Slack app or use existing one
3. Add bot token scopes (e.g., channels:read, chat:write)
4. Install app to workspace
5. Copy Bot User OAuth Token
6. Add tokens to repository secrets

Suggested Configuration

Add the following to your MCP Gateway configuration:

{
  "slack": {
    "type": "stdio",
    "container": "mcp/slack",
    "env": {
      "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
      "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
    }
  }
}

Next Steps

• Create Slack app and obtain bot token
• Add SLACK_BOT_TOKEN to repository secrets
• Add SLACK_TEAM_ID to repository secrets
• Update stress test configuration
• Verify server works in next nightly test

---

Generated by Nightly MCP Stress Test
Test Session: stress-test-20260204-180602

AI generated by Nightly MCP Server Stress Test

<agent_instructions>Update the stress test agentic workflow to add a secret for SLACK_BOT_TOKEN and SLACK_TEAM_ID</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Custom agent used: agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing

• Fixes [mcp-stress-test] Slack MCP Server requires SLACK_BOT_TOKEN authentication #655

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[lpcox]

@copilot only change the .md files. drop updates to the .lock.yml file since it will be regenerated

[Copilot]

@copilot only change the .md files. drop updates to the .lock.yml file since it will be regenerated

Done. Reverted the .lock.yml file changes - now only the .md file is modified. The lock file will be regenerated during compilation.

Commit: 12bf2e0

[Copilot]

Pull request overview

This PR adds Slack authentication configuration to the nightly MCP stress test workflow to resolve authentication failures detected during testing. The change enables the Slack MCP server to authenticate using bot tokens stored in GitHub repository secrets.

Changes:

• Added env section to the Slack MCP server configuration with SLACK_BOT_TOKEN and SLACK_TEAM_ID environment variables

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.