Skip to content

feat: support auth block in MCP servers config in agents#24770

Open
TanmayVartak wants to merge 2 commits intogoogle-gemini:mainfrom
TanmayVartak:feat/mcp-auth-agent-config
Open

feat: support auth block in MCP servers config in agents#24770
TanmayVartak wants to merge 2 commits intogoogle-gemini:mainfrom
TanmayVartak:feat/mcp-auth-agent-config

Conversation

@TanmayVartak
Copy link
Copy Markdown

This PR adds support for the 'auth' block in the 'mcp_servers' section of agent markdown files, allowing local agents to configure Google credentials or OAuth for MCP servers.

@TanmayVartak TanmayVartak requested a review from a team as a code owner April 6, 2026 19:43
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces authentication capabilities for MCP servers defined in local agent markdown files. By adding an 'auth' block, users can now configure Google credentials or OAuth settings directly within their agent definitions, enabling secure access to MCP servers that require authentication.

Highlights

  • Authentication Support: Added support for an 'auth' block within the 'mcp_servers' configuration in agent markdown files.
  • Configuration Schema: Updated Zod schemas to validate 'google-credentials' and 'oauth' authentication types for MCP servers.
  • Agent Loader Logic: Updated the agent loader to map the new authentication configuration to the internal MCPServerConfig structure.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces support for authentication configurations in MCP servers within agent definitions. It updates the mcpServerSchema to include google-credentials and oauth authentication types and modifies the markdownToAgentDefinition function to correctly map these configurations to MCPServerConfig. Additionally, a new test case was added to verify the conversion of MCP servers with Google credentials. I have no feedback to provide.

@gemini-cli gemini-cli bot added the status/need-issue Pull requests that need to have an associated issue. label Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/need-issue Pull requests that need to have an associated issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant