Skip to directory

Secure Source Manager MCP

Google Cloud

Streamable HTTP38 documented tools5

About Secure Source Manager MCP

Google Cloud managed MCP server for Secure Source Manager. Exact tool names and accessible operations depend on the published server reference and configured Google Cloud permissions.

Connection and setup
Hosting
Google-managed remote
Transport
Streamable HTTP
Endpoint
https://securesourcemanager.us-central1.rep.googleapis.com/mcp/code_review
Authentication
Google Cloud authentication: OAuth 2.0 using Application Default Credentials (ADC) in supported Google clients, or a client OAuth ID/secret or bearer token in compatible third-party clients. The principal needs mcp.tools.call plus the underlying product permissions; API key authentication is only available for services that explicitly support it.

Requirements

  • A Google Cloud project and access to the target product/resource.
  • Enable this MCP service and its underlying Google Cloud API as required by the product guide.
  • An MCP client that supports Streamable HTTP.
  • An identity with the MCP Tool User role (roles/mcp.toolUser) or equivalent mcp.tools.call permission, plus permissions for the underlying product operations.

Setup steps

  1. Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint.
  2. In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it.
  3. Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client.
  4. Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations.
  5. Add securesourcemanager.us-central1.rep.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in.
  6. Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset.
Tools 38

38 tools span instances, repositories, branches, hooks, pull requests/comments and IAM. Writes can create or alter code/repositories, merge pull requests, change branch protections and permissions. Remote MCP is Preview and regional; toolsets separate repository/PR/branch-rule/hook/instance operations. Review diffs and target repo before writes.

  • close_pull_request
    01
  • create_pull_request
    02
  • list_pull_request_file_diffs
    03
  • list_pull_requests
    04
  • merge_pull_request
    05
  • open_pull_request
    06
  • update_pull_request
    07
  • create_pull_request_comment
    08
  • delete_pull_request_comment
    09
  • get_pull_request_comment
    10
  • list_pull_request_comments
    11
  • resolve_pull_request_comments
    12
  • unresolve_pull_request_comments
    13
  • update_pull_request_comment
    14
  • get_instance
    15
  • list_instances
    16
  • create_repository
    17
  • get_repository
    18
  • list_repositories
    19
  • update_repository
    20
  • create_branch_rule
    21
  • delete_branch_rule
    22
  • get_branch_rule
    23
  • list_branch_rules
    24
  • update_branch_rule
    25
  • create_hook
    26
  • delete_hook
    27
  • get_hook
    28
  • list_hooks
    29
  • update_hook
    30
  • get_pull_request
    31
  • batch_create_pull_request_comments
    32
  • get_securesourcemanager_instance_iam_policy
    33
  • set_securesourcemanager_instance_iam_policy
    34
  • test_securesourcemanager_instance_iam_permissions
    35
  • get_securesourcemanager_repository_iam_policy
    36
  • set_securesourcemanager_repository_iam_policy
    37
  • test_securesourcemanager_repository_iam_permissions
    38
Limitations and notes
  • Google marks this service Preview in its supported-products catalog.
Original sources
  • official server catalog

    Official Google Cloud catalog lists this product as an available remote MCP server.

  • official setup guide

    Google Cloud describes remote MCP client setup, Streamable HTTP transport, supported authentication options, and ADC setup.

  • official authentication guide

    Google documents supported identity types and authorization requirements for Google Cloud MCP calls.

  • official source

    Official Google Cloud primary MCP documentation checked 2026-10-28.

  • official source

    Official Google Cloud primary MCP documentation checked 2026-10-28.

Documentation checked 2026-10-28. Connection has not been runtime tested.