Runpod integration for AI agents.
Runpod integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Runpod tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Runpod actions, managed and audited.
Your user connects Runpod once; your agent can then aI infrastructure with on-demand GPUs and serverless compute. Run training, inference, and batch workloads on the cloud with Runpod — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Runpod access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Runpod tools.
37 tools are generated from the published Runpod catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 37 tools. All published catalog entries are included in this page's server-rendered HTML.
- Create a new container registry auth
- Create a new container registry auth.
- container registry auths
- Create a new endpoint
- Create a new endpoint.
- endpoints
- Create a new network volume
- Create a new network volume.
- network volumes
- Create a new Pod
- Creates a new [Pod](#/components/schemas/Pod) and optionally deploys it.
- pods
- Create a new template
- Create a new template.
- templates
- Delete a container registry auth
- Delete a container registry auth.
- container registry auths
- Delete an endpoint
- Delete an endpoint.
- endpoints
- Delete a network volume
- Delete a network volume.
- network volumes
- Delete a Pod
- Delete a Pod.
- pods
- Delete a template
- Delete a template.
- templates
- Serverless billing history
- Retrieve billing information about your Serverless endpoints.
- billing
- Find a container registry auth by ID
- Returns a single container registry auth.
- container registry auths
- Documentation Page
- Interactive API documentation.
- docs
- Find an endpoint by ID
- Returns a single endpoint.
- endpoints
- Find a network volume by ID
- Returns a single network volume.
- network volumes
- OpenAPI 3.0 schema
- The OpenAPI 3.0 schema.
- docs
- Find a Pod by ID
- Returns a single Pod.
- pods
- Find a template by ID
- Returns a single template.
- templates
- List container registry auths
- Returns a list of container registry auths.
- container registry auths
- List endpoints
- Returns a list of endpoints.
- endpoints
- List network volumes
- Returns a list of network volumes.
- network volumes
- List Pods
- Returns a list of Pods.
- pods
- List templates
- Returns a list of templates.
- templates
- Network volume billing history
- Retrieve billing information about your network volumes.
- billing
- Pod billing history
- Retrieve billing information about your Pods.
- billing
- Update an endpoint
- Update an endpoint - synonym for PATCH /endpoints/{endpointId}.
- endpoints
- Update a network volume
- Update a network volume - synonym for PATCH /networkvolumes/{networkVolumeId}.
- network volumes
- Update a Pod
- Update a Pod - synonym for PATCH /pods/{podId}.
- pods
- Update a template
- Update a template - synonym for PATCH /templates/{templateId}.
- templates
- Reset a Pod
- Reset a Pod.
- pods
- Restart a Pod
- Restart a Pod.
- pods
- Start or resume a Pod
- Start or resume a Pod.
- pods
- Stop a Pod
- Stop a Pod.
- pods
- Update an endpoint
- Update an endpoint.
- endpoints
- Update a network volume
- Update a network volume.
- network volumes
- Update a Pod
- Update a Pod, potentially triggering a reset.
- pods
- Update a template
- Update a template.
- templates
Runpod integration, answered
- How do AI agents use Runpod through Open Connector?
- Your user connects Runpod once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Runpod tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Runpod MCP server?
- Yes. Open Connector can serve Runpod as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Runpod actions with credentials injected server-side.
- Where do Runpod credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Runpod — keep the keys.
Open source, self-hostable, with Runpod credentials that never leave your infrastructure. Run it from source today.