Porter PaaS MCP Server for Windsurf 10 tools — connect in under 2 minutes
Windsurf brings agentic AI coding to a purpose-built IDE. Connect Porter PaaS through Vinkius and Cascade will auto-discover every tool. ask questions, generate code, and act on live data without leaving your editor.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Porter PaaS and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"porter-paas": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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.
Windsurf's Cascade agent chains multiple Porter PaaS tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 10 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
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 Windsurf 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 Windsurf via MCP
Follow these steps to integrate the Porter PaaS MCP Server with Windsurf.
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
Add the server
Paste the JSON configuration above into mcp_config.json
Save and reload
Windsurf will detect the new server automatically
Start using Porter PaaS
Open Cascade and ask: "Using Porter PaaS, help me...". 10 tools available
Why Use Windsurf with the Porter PaaS MCP Server
Windsurf provides unique advantages when paired with Porter PaaS through the Model Context Protocol.
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
JSON-based configuration means zero code changes: paste a URL, reload, and all 10 tools are immediately available
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
Porter PaaS + Windsurf Use Cases
Practical scenarios where Windsurf combined with the Porter PaaS MCP Server delivers measurable value.
Automated code generation: ask Cascade to fetch data from Porter PaaS and generate models, types, or handlers based on real API responses
Live debugging: query Porter PaaS tools mid-session to inspect production data while debugging without leaving the editor
Documentation generation: pull schema information from Porter PaaS and have Cascade generate comprehensive API docs automatically
Rapid prototyping: combine Porter PaaS data with Cascade's code generation to scaffold entire features in minutes
Porter PaaS MCP Tools for Windsurf (10)
These 10 tools become available when you connect Porter PaaS to Windsurf via MCP:
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
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
get_cluster
Inspect deep cloud credentials generating a specific K8s Cluster
get_project
Perform structural extraction of metadata linked to a Porter Project
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
list_clusters
Exposes crucial execution zones hosting absolute memory nodes. List underlying target cloud Kubernetes definitions bounds to Porter
list_environments
Extract logic isolation environments overlapping the Cluster
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
list_projects
Fetches indispensable integer `projectId` arrays coordinating everything strictly downstream inside AWS/GCP clusters. Identify base Porter PaaS organizational scopes
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 Windsurf
Ready-to-use prompts you can give your Windsurf agent to start working with Porter PaaS immediately.
"List all applications currently running in cluster ID 5 on the Production environment."
"The queue worker is completely hung. Please perform a forceful restart of the `async-worker` app."
"We just built a hotfix on main. Deploy the image tag `d83a1b1` strictly onto `portal-frontend`."
Troubleshooting Porter PaaS MCP Server with Windsurf
Common issues when connecting Porter PaaS to Windsurf through the Vinkius, and how to resolve them.
Server not connecting
Porter PaaS + Windsurf FAQ
Common questions about integrating Porter PaaS MCP Server with Windsurf.
How does Windsurf discover MCP tools?
mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.Can Cascade chain multiple MCP tool calls?
Does Windsurf support multiple MCP servers?
mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.Connect Porter PaaS with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Porter PaaS to Windsurf
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.