test(source/http): create MCP integration tests

[anubhav756]

Overview

This PR adds the mapped integration tests for HTTP tools using the new native MCP harness.

Changes

• Created tests/http/http_mcp_test.go and ported all relevant tests from the legacy http_integration_test.go to use the /mcp pathway.
• Includes covered positive paths, negative paths, and optional query parameter variations.

Checklist

• Ensure the tests and linter pass

[gemini-code-assist]

Summary of Changes

Hello, 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 updates the HTTP tool integration tests to leverage a native MCP JSON-RPC protocol for interacting with tools. This change simplifies the testing framework by abstracting the underlying communication mechanism into a dedicated helper, making tests more consistent and easier to maintain. As a result of this refactoring, the continuous integration configuration has been substantially reduced, removing many specific test steps and secret definitions that are no longer relevant to the streamlined HTTP test suite.

Highlights

• Migration to Native MCP JSON-RPC: The HTTP tool integration tests have been migrated to use a native MCP JSON-RPC protocol for tool invocation and listing, moving away from direct HTTP API endpoints.
• Test Refactoring: Existing HTTP tool invocation tests, including runQueryParamInvokeTest and runAdvancedHTTPInvokeTest, were refactored to utilize a new InvokeMCPTool helper function, standardizing test logic and error handling.
• CI Configuration Streamlining: The .ci/integration.cloudbuild.yaml file was significantly streamlined by removing numerous individual integration test steps and their associated secret environment variables, focusing the CI on the updated HTTP test approach.

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

[gemini-code-assist]

Code Review

This pull request refactors the HTTP integration tests to utilize native MCP JSON-RPC protocol invocation helpers, improving the testing methodology for HTTP tools. However, a critical issue has been identified where the changes inadvertently remove almost all other integration tests from the CI pipeline, which could severely impact test coverage and needs to be addressed. Additionally, there's an opportunity to improve code maintainability by extracting duplicated error handling logic within the HTTP integration tests into a shared helper function.

[Yuan325]

Please rebase this after updating the #2828 PR :) Thank you.

[Yuan325]

Awesome, thank you!! LGTM :)

[github-actions]

🧨 Preview deployments removed.

Cloudflare Pages environments for pr-2842 have been deleted.