> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Porter

> Give the Sazabi agent tools to read Porter application logs, metrics, deploy status, and cluster state, and to manage Porter apps.

[All Porter integration capabilities](https://docs.sazabi.com/catalogs/integrations/porter)

## 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**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Porter in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Authorize

Start the connection; Sazabi redirects you to Porter to sign in and authorize, then back.

## Set up with the CLI

You can also connect Porter with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)).

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

```bash theme={"system"}
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**](https://app.sazabi.com/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**](https://app.sazabi.com/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**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.