mcp-ge

Deploys authenticated MCP servers for Gemini Enterprise Agent Designer on Cloud Run.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill mcp-ge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-ge
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/mcp-ge
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill mcp-ge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of reliably deploying and authenticating custom MCP servers for Gemini Enterprise Agent Designer without GE surprises like unsupported transports, broken OAuth flows, or cached tool schemas.

Core Features & Use Cases

  • Org-policy and data-store setup: Handles the required Google Cloud org policy override and GE data store configuration needed to register an MCP server endpoint.
  • OAuth identity + production-ready token behavior: Specifies environment variables, exact redirect URI matching, and a token endpoint that supports both authorization_code and refresh_token with sufficiently long-lived JWTs.
  • GE-compatible MCP architecture constraints: Ensures tools are registered directly (no meta-tool indirection), uses StreamableHTTP only, and supports zero-parameter identity resolution via JWT-derived email.
  • Deployment guidance for production pitfalls: Includes checklist items for scaling constraints (in-memory OAuth state), Cloud Run build context gotchas, and common GE UI/log symptoms.

Quick Start

Activate the mcp-ge skill when you need to deploy a new MCP server for Gemini Enterprise that uses StreamableHTTP and implements the required GE OAuth double-flow with a /token endpoint that supports refresh_token.

Frequently Asked Questions about mcp-ge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a custom MCP server on Cloud Run for Gemini Enterprise?

To deploy a custom MCP server on Cloud Run for Gemini Enterprise, you must configure Google Cloud org policies, set up the GE data store, and use StreamableHTTP transport. Direct tool registration and exact redirect_uri matching are also required.

What OAuth flows are required for Gemini Enterprise MCP server authentication?

Gemini Enterprise MCP server authentication requires a token endpoint supporting both authorization_code and refresh_token grants. The resulting JWT must have a TTL of at least 24 hours, and exact redirect_uri matching is enforced.

Does Gemini Enterprise support SSE transport for MCP tool connectors?

Gemini Enterprise does not support SSE for MCP tool connectors. You must use StreamableHTTP transport exclusively to ensure production compatibility and successful tool registration.

Why does my MCP server fail identity resolution in Gemini Enterprise?

Identity resolution fails when the MCP server lacks zero-parameter JWT-based email extraction. The server must support JWT-derived email identity to resolve users correctly within Gemini Enterprise.

Can I use meta-tool indirection when registering MCP tools with Gemini Enterprise?

Meta-tool indirection is not supported by Gemini Enterprise. You must register tools directly to avoid broken schemas and ensure the Agent Designer recognizes the MCP server endpoints.

What are the limitations of in-memory OAuth state for MCP servers on Cloud Run?

In-memory OAuth state limits horizontal scaling on Cloud Run because instances do not share session data. This architecture constraint requires careful handling of OAuth flows and state management during production onboarding.