2,500+ MCP servers ready to use
Vinkius

Porter PaaS MCP Server for Mastra AI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Porter PaaS through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "porter-paas": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Porter PaaS Agent",
    instructions:
      "You help users interact with Porter PaaS " +
      "using 10 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Porter PaaS?"
  );
  console.log(result.text);
}

main();
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.

Mastra's agent abstraction provides a clean separation between LLM logic and Porter PaaS tool infrastructure. Connect 10 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the Porter PaaS MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 10 tools from Porter PaaS via MCP

Why Use Mastra AI with the Porter PaaS MCP Server

Mastra AI provides unique advantages when paired with Porter PaaS through the Model Context Protocol.

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Porter PaaS without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Porter PaaS tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

Porter PaaS + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the Porter PaaS MCP Server delivers measurable value.

01

Automated workflows: build multi-step agents that query Porter PaaS, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Porter PaaS as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Porter PaaS on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Porter PaaS tools alongside other MCP servers

Porter PaaS MCP Tools for Mastra AI (10)

These 10 tools become available when you connect Porter PaaS to Mastra AI 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 Mastra AI

Ready-to-use prompts you can give your Mastra AI 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 Mastra AI

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

01

createMCPClient not exported

Install: npm install @mastra/mcp

Porter PaaS + Mastra AI FAQ

Common questions about integrating Porter PaaS MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Porter PaaS to Mastra AI

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