Bring Kubernetes
to VS Code Copilot
Create your Vinkius account to connect Porter PaaS to VS Code Copilot and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Porter PaaS MCP Server?
Connect your Porter account to any AI agent and take full programmatic control over your Kubernetes infrastructure natively.
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)
How it works
- Subscribe to this server
- Enter your Porter API Token
- Start managing your clusters straight from Claude, Cursor, or any MCP client
No pulling KUBECONFIG files, authenticating via cloud CLI tools, or navigating dashboards. Your orchestration lives in chat.
Who is this for?
- DevOps Engineers — quickly restart crashing services and audit cluster architectures on the fly
- Backend Developers — rollback image tags and orchestrate quick deployments directly from standard chat
- Engineering Leads — inspect resource mapping and isolate distinct staging environments instantly
Built-in capabilities (10)
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
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
Inspect deep cloud credentials generating a specific K8s Cluster
Perform structural extraction of metadata linked to a Porter Project
Discovers precisely which App routing identities expose `porter.run` subdomains or linked target custom apex mappings. Inventory deployed discrete Applications mapping to a Cluster
Exposes crucial execution zones hosting absolute memory nodes. List underlying target cloud Kubernetes definitions bounds to Porter
Extract logic isolation environments overlapping the Cluster
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
Fetches indispensable integer `projectId` arrays coordinating everything strictly downstream inside AWS/GCP clusters. Identify base Porter PaaS organizational scopes
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
Why VS Code Copilot?
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.
- —
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 in VS Code Copilot
Why run Porter PaaS with Vinkius?
The Porter PaaS connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Porter PaaS using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Porter PaaS and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Porter PaaS to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Porter PaaS for VS Code Copilot
Every request between VS Code Copilot and Porter PaaS is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can my AI automatically deploy an urgent hotfix tag?
Yes. If a specific commit tag needs to be rolled out bypassing regular CI delays, simply command the AI to deploy_app_tag providing the target container suffix. It issues direct orchestration commands triggering an absolute image update inside Kubernetes immediately.
Can the agent check internal Helm variables for external addons?
Absolutely. Using the list_helm_releases tool, your agent analyzes raw orchestrator chart variables inside the cluster's namespace. It is invaluable for diagnosing why your Postgres Helm initialization is misbehaving.
Is it safe to orchestrate infrastructure boundaries with AI?
Yes! The token you provide is inherently scoped to the exact projects authorized in the Porter Dashboard. The AI strictly respects the platform's isolation, ensuring you only restart or query bounded namespace assets.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
GoCardless
12 toolsCollect recurring payments directly from bank accounts with automated direct debit that reduces failed payment rates.

CData Connect Cloud
8 toolsUniversal Data Gateway mapping explicitly proxy structures parsing SQL schemas dynamically connecting APIs natively.

Gitpod
26 toolsAutomate cloud development environments — create, start, and manage Gitpod workspaces and organizations directly from any AI agent.

Nanoid Generator
1 toolsGenerate unique, URL-safe IDs that are 2x faster than UUID, fit in 118 bytes, and use cryptographic randomness. 40M+ weekly downloads.
