Porter PaaS MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
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.
GitHub Copilot Agent mode brings Porter PaaS data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the 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 VS Code Copilot 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 VS Code Copilot via MCP
Follow these steps to integrate the Porter PaaS MCP Server with VS Code Copilot.
Create MCP config
Create a .vscode/mcp.json file in your project root
Add the server config
Paste the JSON configuration above
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Start using Porter PaaS
Ask Copilot: "Using Porter PaaS, help me...". 10 tools available
Why Use VS Code Copilot with the Porter PaaS MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Porter PaaS through the Model Context Protocol.
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Porter PaaS + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Porter PaaS MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Porter PaaS MCP Tools for VS Code Copilot (10)
These 10 tools become available when you connect Porter PaaS to VS Code Copilot 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 VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot
Common issues when connecting Porter PaaS to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Porter PaaS + VS Code Copilot FAQ
Common questions about integrating Porter PaaS MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.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 VS Code Copilot
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.