docs: migration of core package samples from go sdk by AnmolShukla2002 · Pull Request #2330 · googleapis/mcp-toolbox

AnmolShukla2002 · 2026-01-19T09:20:11Z

This PR migrates the Go SDK documentation and core technical samples from the [mcp-toolbox-sdk-go] repository to the main genai-toolbox documentation site. This consolidation ensures that conceptual guides, package overviews, and interactive code examples are available in a centralized "one-stop-shop".

gemini-code-assist · 2026-01-19T09:20:29Z

Summary of Changes

Hello @AnmolShukla2002, I'm Gemini Code Assist¹! 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 significantly enhances the documentation for the MCP Toolbox Go SDK's core package. It provides developers with a centralized and comprehensive resource for understanding the SDK's capabilities, from basic setup and tool interaction to advanced topics like secure authentication mechanisms and flexible parameter binding. Furthermore, it offers ready-to-use integration samples for leading AI orchestration frameworks, streamlining the development of intelligent applications using the Toolbox.

Highlights

Comprehensive Go SDK Documentation: Introduces a new, detailed documentation page for the MCP Toolbox Go SDK's core package, covering installation, usage, and advanced features.
Authentication Guides: Provides in-depth guidance on both client-to-server authentication (e.g., for Cloud Run deployments) and tool-level authentication, including token retrieval and configuration options.
Parameter Binding Functionality: Explains how to bind static or dynamic values to tool parameters, enhancing security and control over tool invocation.
Orchestration Framework Integration Samples: Includes practical code examples demonstrating how to integrate the Go SDK with popular AI orchestration frameworks like Google GenAI, LangChain Go, and OpenAI Go.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

gemini-code-assist

Code Review

This pull request adds extensive documentation and samples for the Go SDK core package. The documentation is comprehensive, but I've found several issues in the code samples, including incomplete examples, incorrect API usage, unhandled errors, and typos. These issues could confuse users or cause their code to fail if they copy the examples. I've left specific comments with suggestions for fixes. Addressing these will greatly improve the quality and usability of the documentation.

github-actions · 2026-01-19T09:24:12Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

anubhav756

Can we have major sections added as separate pages under the SDKs' sections?

anubhav756 · 2026-01-19T10:02:05Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

github-actions · 2026-01-29T10:20:13Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

github-actions · 2026-01-29T10:49:18Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

AnmolShukla2002 · 2026-01-29T10:57:17Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

I guess docs reorganization strategy states that we will "treat each SDK repository as the source of truth for its own API reference". While the docsite serves as the "one-stop-shop" for conceptual guides, the github links serve as the technical reference point until our auto-generated API subdomains are fully live. I am not sure on this, let me know your thoughts?

anubhav756 · 2026-01-29T12:39:30Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

I guess docs reorganization strategy states that we will "treat each SDK repository as the source of truth for its own API reference". While the docsite serves as the "one-stop-shop" for conceptual guides, the github links serve as the technical reference point until our auto-generated API subdomains are fully live. I am not sure on this, let me know your thoughts?

Sounds good! Let’s link directly to the github source files until we have the API ref docsite up.

However for links like those under “Which package should I use?”, I guess I was assuming the links from core, tbadk and tbgenkit could be linked to the packages’ respective pages to the guidance docs that I assume we would be adding to the main docsite (just like we have done for the core package). Currently they seem to link to the github source code (unless it’s intentional because I see the core package guidance page is linked at the bottom of that page, but just thinking what if we also link the guidance pages in that section as well). Thoughts?

anubhav756

LGTM, given we address the bot comments and link checker error as well. Optionally, adding a PR description might help as well.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

github-actions · 2026-01-30T05:08:03Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

AnmolShukla2002 · 2026-01-30T08:45:53Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

I guess docs reorganization strategy states that we will "treat each SDK repository as the source of truth for its own API reference". While the docsite serves as the "one-stop-shop" for conceptual guides, the github links serve as the technical reference point until our auto-generated API subdomains are fully live. I am not sure on this, let me know your thoughts?

Sounds good! Let’s link directly to the github source files until we have the API ref docsite up.

However for links like those under “Which package should I use?”, I guess I was assuming the links from core, tbadk and tbgenkit could be linked to the packages’ respective pages to the guidance docs that I assume we would be adding to the main docsite (just like we have done for the core package). Currently they seem to link to the github source code (unless it’s intentional because I see the core package guidance page is linked at the bottom of that page, but just thinking what if we also link the guidance pages in that section as well). Thoughts?

yes made these changes!

AnmolShukla2002 · 2026-01-30T08:47:49Z

LGTM, given we address the bot comments and link checker error as well. Optionally, adding a PR description might help as well.

Bot's comments are mostly regarding the sample...I am not sure If I should make these changes as it would then defer from the sample in the Sdk repos?

github-actions · 2026-01-30T08:48:25Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

Co-authored-by: Anubhav Dhawan <anubhavdhawan@google.com>

github-actions · 2026-02-03T09:25:22Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

github-actions · 2026-02-04T07:07:57Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

github-actions · 2026-02-04T08:52:56Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

anubhav756 · 2026-02-04T13:23:26Z

LGTM, given we address the bot comments and link checker error as well. Optionally, adding a PR description might help as well.

Bot's comments are mostly regarding the sample...I am not sure If I should make these changes as it would then defer from the sample in the Sdk repos?

Can we apply any grammatical or any other minor suggestions from the bot, without affecting the functionality?

AnmolShukla2002 · 2026-02-05T05:05:46Z

LGTM, given we address the bot comments and link checker error as well. Optionally, adding a PR description might help as well.

Bot's comments are mostly regarding the sample...I am not sure If I should make these changes as it would then defer from the sample in the Sdk repos?

Can we apply any grammatical or any other minor suggestions from the bot, without affecting the functionality?

Okay sure!

github-actions · 2026-02-05T05:26:34Z

🧨 Preview deployments removed.

Related PRs : [Core] #2330 [tbADK] #2393 [tbGenkit] #2394 --------- Co-authored-by: Anubhav Dhawan <anubhavdhawan@google.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

docs: migration of core package samples from go sdk

c72e205

AnmolShukla2002 requested a review from a team January 19, 2026 09:20

blunderbuss-gcf bot assigned Yuan325 Jan 19, 2026

AnmolShukla2002 assigned AnmolShukla2002 and unassigned Yuan325 Jan 19, 2026

AnmolShukla2002 requested review from anubhav756 and dishaprakash January 19, 2026 09:21

gemini-code-assist bot reviewed Jan 19, 2026

View reviewed changes

AnmolShukla2002 mentioned this pull request Jan 19, 2026

docs: migration of Go Sdk docs #2292

Merged

anubhav756 reviewed Jan 19, 2026

View reviewed changes

anubhav756 requested changes Jan 19, 2026

View reviewed changes

Comment thread docs/en/sdks/go-sdk/core/_index.md Outdated

Comment thread docs/en/sdks/go-sdk/core/_index.md Outdated

Comment thread docs/en/sdks/go-sdk/core/_index.md Outdated

refactored sample section

aa121e1

align docsy/hugo theme for tags

8e4cd41

anubhav756 approved these changes Jan 29, 2026

View reviewed changes

Update docs/en/sdks/go-sdk/core/_index.md

569b988

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

update framework links to docsite

a49191f

anubhav756 approved these changes Feb 2, 2026

View reviewed changes

Comment thread docs/en/sdks/go-sdk/core/_index.md

Comment thread docs/en/sdks/go-sdk/_index.md

anubhav756 self-requested a review February 2, 2026 12:30

anubhav756 requested changes Feb 2, 2026

View reviewed changes

Comment thread docs/en/sdks/go-sdk/core/_index.md

anubhav756 requested changes Feb 2, 2026

View reviewed changes

Comment thread docs/en/sdks/go-sdk/core/_index.md Outdated

Update docs/en/sdks/go-sdk/core/_index.md

4ff4466

Co-authored-by: Anubhav Dhawan <anubhavdhawan@google.com>

refactor docs

87b6dc1

rename heading

e3afb14

anubhav756 approved these changes Feb 4, 2026

View reviewed changes

AnmolShukla2002 merged commit c8818ff into migrate-go-sdk Feb 5, 2026
12 of 13 checks passed

AnmolShukla2002 deleted the migrate-go-sdk-core branch February 5, 2026 05:25

Conversation

AnmolShukla2002 commented Jan 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gemini-code-assist bot commented Jan 19, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Jan 19, 2026

Uh oh!

anubhav756 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

anubhav756 commented Jan 19, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Jan 29, 2026

Uh oh!

github-actions bot commented Jan 29, 2026

Uh oh!

AnmolShukla2002 commented Jan 29, 2026

Uh oh!

anubhav756 commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anubhav756 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

AnmolShukla2002 commented Jan 30, 2026

Uh oh!

AnmolShukla2002 commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Feb 3, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

anubhav756 commented Feb 4, 2026

Uh oh!

AnmolShukla2002 commented Feb 5, 2026

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

AnmolShukla2002 commented Jan 19, 2026 •

edited

Loading

anubhav756 left a comment •

edited

Loading

anubhav756 commented Jan 29, 2026 •

edited

Loading

anubhav756 left a comment •

edited

Loading