MCP server to deploy code to Google Cloud Run

Created By
GoogleCloudPlatforma year ago
MCP server to deploy apps to Cloud Run
Overview

What is Cloud Run MCP?

Cloud Run MCP is a server designed to deploy applications to Google Cloud Run using MCP-compatible AI agents.

How to use Cloud Run MCP?

To use Cloud Run MCP, you can deploy applications from AI-powered IDEs or AI assistant apps by following the provided commands and configurations in the documentation.

Key features of Cloud Run MCP?

  • Deploy applications to Google Cloud Run easily.
  • Supports deployment from various AI tools and SDKs.
  • Provides commands for local and remote server setups.

Use cases of Cloud Run MCP?

  1. Deploying web applications to Google Cloud Run.
  2. Integrating with AI-assisted development environments.
  3. Managing deployments securely with IAM authentication.

FAQ from Cloud Run MCP?

  • Is Cloud Run MCP free to use?

Yes! Cloud Run MCP is free to use, but you may incur charges from Google Cloud services.

  • Can I deploy any type of application?

Yes! You can deploy various types of applications as long as they are compatible with Google Cloud Run.

  • How do I secure my deployments?

Use IAM authentication to secure your connection to the MCP server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GoogleCloudPlatform
Star
110
Language
JavaScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago