Add BRAVE_API_KEY authentication to brave-search MCP server

[Copilot]

Nightly stress test detected the Brave Search MCP server requires API key authentication. Added BRAVE_API_KEY secret configuration to the stress test workflow.

Changes

• Workflow configuration: Added BRAVE_API_KEY environment variable to brave-search MCP server in nightly-mcp-stress-test.md

brave-search:
  type: stdio
  container: "mcp/brave-search"
  env:
    BRAVE_API_KEY: "${{ secrets.BRAVE_API_KEY }}"

Follows existing pattern used for GitHub MCP server authentication. Repository admin needs to add BRAVE_API_KEY to secrets for next stress test run. The workflow lock file will be regenerated automatically on next compilation.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[mcp-stress-test] Brave Search MCP Server requires BRAVE_API_KEY authentication</issue_title>
<issue_description># MCP Server Authentication Required: Brave Search

The nightly stress test detected that the Brave Search 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/brave-search

Required Authentication Token

Environment Variable: BRAVE_API_KEY

Token Type: API Key

How to Obtain:

1. Visit: (brave.com/redacted)
2. Sign up for Brave Search API access
3. Generate an API key
4. Add to repository secrets as BRAVE_API_KEY

Suggested Configuration

Add the following to your MCP Gateway configuration:

{
  "brave-search": {
    "type": "stdio",
    "container": "mcp/brave-search",
    "env": {
      "BRAVE_API_KEY": "${BRAVE_API_KEY}"
    }
  }
}

Next Steps

• Obtain BRAVE_API_KEY token
• Add token 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 a BRAVE_API_KEY</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] Brave Search MCP Server requires BRAVE_API_KEY authentication #654

---

✨ 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 all .lock.yml file changes and kept only the .md file modification in commit 2049842.

[Copilot]

Pull request overview

This PR adds API key authentication for the Brave Search MCP server in the nightly stress test workflow. The change was triggered by a stress test failure that detected the Brave Search MCP server requires authentication.

Changes:

• Added BRAVE_API_KEY environment variable configuration to the brave-search MCP server in the stress test workflow

---

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