Add GOOGLE_APPLICATION_CREDENTIALS to gdrive MCP server

[Copilot]

Nightly stress test detected gdrive MCP server failing on missing OAuth credentials.

Changes

• Added env.GOOGLE_APPLICATION_CREDENTIALS to gdrive MCP server config in nightly-mcp-stress-test.md

gdrive:
  type: stdio
  container: "mcp/gdrive"
  env:
    GOOGLE_APPLICATION_CREDENTIALS: "${{ secrets.GOOGLE_APPLICATION_CREDENTIALS }}"

Post-merge

Repository maintainers need to add GOOGLE_APPLICATION_CREDENTIALS to repository secrets with Google OAuth credentials JSON.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[mcp-stress-test] Google Drive MCP Server requires OAuth credentials</issue_title>
<issue_description># MCP Server Authentication Required: Google Drive

The nightly stress test detected that the Google Drive 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/gdrive

Required Authentication Token

Environment Variable: Google OAuth credentials (typically GOOGLE_APPLICATION_CREDENTIALS or OAuth token)

Token Type: OAuth 2.0 Credentials

How to Obtain:

1. Visit: (console.cloud.google.../redacted)
2. Create a new project or use existing one
3. Enable Google Drive API
4. Create OAuth 2.0 credentials
5. Download credentials JSON
6. Add to repository secrets

Suggested Configuration

Add the following to your MCP Gateway configuration:

{
  "gdrive": {
    "type": "stdio",
    "container": "mcp/gdrive",
    "env": {
      "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
    }
  }
}

Next Steps

• Create Google Cloud project
• Enable Google Drive API
• Obtain OAuth credentials
• Add credentials 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 GOOGLE_APPLICATION_CREDENIALS for gdrive</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] Google Drive MCP Server requires OAuth credentials #652

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR adds Google OAuth credentials configuration to the gdrive MCP server to fix authentication failures detected by the nightly stress test. The changes enable the gdrive MCP server to authenticate with Google Drive API.

Changes:

• Added GOOGLE_APPLICATION_CREDENTIALS environment variable to gdrive MCP server configuration in both the workflow definition (.md) and compiled lock file (.yml)
• Updated Docker command to pass the credentials environment variable to containers
• Added secret redaction for GOOGLE_APPLICATION_CREDENTIALS to prevent credential exposure in logs

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/nightly-mcp-stress-test.md	Added env configuration with GOOGLE_APPLICATION_CREDENTIALS to gdrive MCP server definition
.github/workflows/nightly-mcp-stress-test.lock.yml	Compiled changes including env variable in step environment, Docker command, JSON config, and secret redaction setup

---

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

[Copilot]

The JSON configuration uses GitHub Actions template syntax directly (${{ secrets.GOOGLE_APPLICATION_CREDENTIALS }}), which is inconsistent with how other environment variables are referenced in this heredoc.

For consistency with the existing pattern (e.g., line 466 which uses \${GITHUB_MCP_SERVER_TOKEN}), this should use the escaped bash variable syntax \${GOOGLE_APPLICATION_CREDENTIALS} instead. The secret is already made available as an environment variable on line 384, so it can be referenced using bash variable expansion.

This approach is more consistent with how the codebase handles environment variables in heredocs and makes the code more maintainable.