pulsemcp scanned Safe content atomic mcp-remote

Google Cloud Run

This MCP server enables AI agents to deploy applications directly to Google Cloud Run through a comprehensive set of deployment tools. Developed by Google Cloud Platform, it provides both local and remote deployment capabilities, supporting file-based deployments (from local filesystem or provided content), automatic project creation with billing account attachment, and service management operations like listing and inspecting Cloud Run services. The implementation handles the complete deployment pipeline including source code packaging, Cloud Build integration for containerization (supporting both Dockerfile and buildpack approaches), Artifact Registry management, and Cloud Run service provisioning with automatic API enablement and resource setup. Designed for AI-assisted development workflows, it allows developers to deploy applications through natural language commands while maintaining proper authentication and project isolation, making it valuable for rapid prototyping, automated deployment pipelines, and AI-powered development environments.

Cognium trust score

20%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-02.

Scan details: Circle-IR · 2026-09-02 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/googlecloudplatform/cloud-run-mcp
Author type: human
Last scanned: 2026-09-02
Updated: 2026-09-02

View source Find related skills

MCP

Resolve Google Cloud Run from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"