Porter

All Porter integration capabilities

About

This is an MCP connector that gives the Sazabi agent tools from Porter's hosted MCP server. Porter authenticates via OAuth with dynamic client registration — you sign in once in the browser and Sazabi refreshes the token thereafter. Access follows the Porter projects the connected account can reach.

What the agent can do:

• Read application logs, deployment status, revisions, and runtime notifications
• Read CPU, memory, and request metrics for applications and node groups
• Inspect clusters, nodes, pods, load balancers, and job runs
• Update, redeploy, and create applications and trigger job runs (turn on read-only mode to block these)

Prerequisites

• A Porter account
• Access to the Porter project whose applications you want to connect

Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.

Set up with the CLI

You can also connect Porter with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).

Porter authenticates over OAuth, so the CLI opens a browser to complete authorization:

sazabi mcp-connectors connect porter

Add --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints the authorization attempt, including the URL to open, without polling for completion. Confirm the result with sazabi mcp-connectors list.

Verify

Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered (for example get_projects, get_app_logs, get_application_status). Then, in a thread, ask the agent to read recent logs for one of your Porter applications and confirm it runs.

Troubleshooting

No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.

Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.

Further reading