2,500+ MCP servers ready to use
Vinkius

Porter PaaS MCP Server for Google ADK 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Porter PaaS as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Vinkius supports streamable HTTP and SSE.

python
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="porter_paas_agent",
    instruction=(
        "You help users interact with Porter PaaS "
        "using 10 available tools."
    ),
    tools=[mcp_tools],
)
Porter PaaS
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Porter PaaS MCP Server

Connect your Porter account to any AI agent and take full programmatic control over your Kubernetes infrastructure natively.

Google ADK natively supports Porter PaaS as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

What you can do

  • Projects & Clusters — List high-level organizational bounds, EKS/GKE clusters, and deployment zones
  • Applications & Environments — Map staging/production namespaces, check active web services, and resolve container requirements
  • Operations — Restart app pods gracefully or forcefully deploy specific image tags when resolving CI/CD breaks
  • Helm Inspections — Check low-level Helm charts behind active components (like Postgres or Redis)

The Porter PaaS MCP Server exposes 10 tools through the Vinkius. Connect it to Google ADK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Porter PaaS to Google ADK via MCP

Follow these steps to integrate the Porter PaaS MCP Server with Google ADK.

01

Install Google ADK

Run pip install google-adk

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Create the agent

Save the code above and integrate into your ADK workflow

04

Explore tools

The agent will discover 10 tools from Porter PaaS via MCP

Why Use Google ADK with the Porter PaaS MCP Server

Google ADK provides unique advantages when paired with Porter PaaS through the Model Context Protocol.

01

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Porter PaaS

03

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

04

Seamless integration with Google Cloud services means you can combine Porter PaaS tools with BigQuery, Vertex AI, and Cloud Functions

Porter PaaS + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Porter PaaS MCP Server delivers measurable value.

01

Enterprise data agents: ADK agents query Porter PaaS and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Porter PaaS tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Porter PaaS regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Porter PaaS

Porter PaaS MCP Tools for Google ADK (10)

These 10 tools become available when you connect Porter PaaS to Google ADK via MCP:

01

deploy_app_tag

Assigns a raw docker registry digest/tag directly causing Kubernetes to perform an absolute image pull orchestrating a fresh deployment state spanning replica boundaries. Forcefully mutate the executed Docker image running internally

02

get_app

Includes explicit CPU metrics requested, RAM limits mapped locally to the JVM/Node instances, and internal registry image hashes resolving at runtime. Analyze architectural bindings orchestrating a specific App

03

get_cluster

Inspect deep cloud credentials generating a specific K8s Cluster

04

get_project

Perform structural extraction of metadata linked to a Porter Project

05

list_apps

Discovers precisely which App routing identities expose `porter.run` subdomains or linked target custom apex mappings. Inventory deployed discrete Applications mapping to a Cluster

06

list_clusters

Exposes crucial execution zones hosting absolute memory nodes. List underlying target cloud Kubernetes definitions bounds to Porter

07

list_environments

Extract logic isolation environments overlapping the Cluster

08

list_helm_releases

Vital for verifying if dependent third-party apps (e.g. Postgres databases or Metabase) deployed aside the primary stack succeeded during installation phases. List underlying operational Helm configurations inside a namespace

09

list_projects

Fetches indispensable integer `projectId` arrays coordinating everything strictly downstream inside AWS/GCP clusters. Identify base Porter PaaS organizational scopes

10

restart_app

Mandatory during severe connection leakage scenarios impacting native processes without modifying the fundamental code layer deployment tag. Instruct the Kubernetes API to bounce the App deployment replicas

Example Prompts for Porter PaaS in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Porter PaaS immediately.

01

"List all applications currently running in cluster ID 5 on the Production environment."

02

"The queue worker is completely hung. Please perform a forceful restart of the `async-worker` app."

03

"We just built a hotfix on main. Deploy the image tag `d83a1b1` strictly onto `portal-frontend`."

Troubleshooting Porter PaaS MCP Server with Google ADK

Common issues when connecting Porter PaaS to Google ADK through the Vinkius, and how to resolve them.

01

McpToolset not found

Update: pip install --upgrade google-adk

Porter PaaS + Google ADK FAQ

Common questions about integrating Porter PaaS MCP Server with Google ADK.

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Connect Porter PaaS to Google ADK

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.