Skip to content
PWR

Integrations

Every integration, with its real status

PWR connects to source control, project trackers, model providers, your own tools, game engines and billing. Each integration below states whether it is verified, in beta against a simulator, or not built yet.

Request early access

Engineers and administrators checking whether PWR fits their stack before they commit to it.

How it works

Integrations, step by step

  1. 01

    Connect source control

    Install the GitHub App and claim the installation for your organization. Repository tokens are minted per use with the narrowest permissions.

  2. 02

    Link your tracker

    Add a Jira Cloud or GitHub Issues connection and link it to a project as import-only or two-way.

  3. 03

    Choose models and keys

    Use PWR Auto, pin a provider and model, or bind your own provider key to an agent.

  4. 04

    Register your tools

    Add MCP servers or custom HTTP tools, approve them, and grant them to the agents that need them.

Available
Implemented and covered by automated tests in the current platform build.
Beta
Implemented; verification against the live external service is still pending.
Upcoming
Planned or in progress. Not usable yet.

Source control and project management

  • GitHub App

    Beta

    Installation claim with proof of control, repository connections, signed and de-duplicated webhooks, and the branch, pull request, CI and merge workflow.

    Verified end to end against a simulated GitHub; verification against live GitHub is pending.

  • GitHub Issues

    Beta

    Import issues by milestone or label, detect dependencies from issue text, and write back comments, labels and pull request links.

    Verified against a simulated GitHub; verification against live GitHub Issues is pending.

  • Jira Cloud with API token

    Beta

    Import by sprint, board or JQL. Write back comments, transitions, labels and remote links. Receive issue webhooks with a shared secret.

    Verified against a simulated Jira Cloud; verification against a live Jira site is pending.

  • Jira Cloud with OAuth

    Beta

    Connect through Atlassian OAuth instead of an API token, with token refresh.

    The flow is scaffolded and tested only against a simulated token endpoint; the real Atlassian consent flow is unverified.

  • Linear

    Upcoming

    The connector interface is declared. No implementation exists yet.

  • Notion

    Upcoming

    The connector interface is declared. No implementation exists yet.

Model providers

PWR runs third-party models. Provider keys are encrypted at rest and can be your own.

  • Anthropic Agent SDK

    Available

    The primary agent runtime with tool allowlists, workspace confinement and usage reporting.

    Verified with real model runs. The brokered customer-key path is covered by simulators only.

  • Anthropic Messages API

    Beta

    A tool-calling adapter with streaming and cache-aware usage reporting.

    Verified against in-repo provider simulators; verification against the live provider is pending.

  • OpenAI

    Beta

    Chat Completions and Responses adapters with tool calling, streaming and reasoning-effort settings.

    Verified against in-repo provider simulators; verification against the live provider is pending.

  • Google Gemini

    Beta

    A tool-calling adapter with streaming and thinking-budget settings.

    Verified against in-repo provider simulators; verification against the live provider is pending.

  • xAI Grok

    Beta

    A tool-calling adapter with streaming.

    Verified against in-repo provider simulators; verification against the live provider is pending.

  • OpenAI Codex CLI

    Upcoming

    An interface exists but the runtime is not executable. It requires the CLI on the worker image and has not been validated.

Tools and engines

  • MCP servers

    Available

    Tool discovery with pinned server identity, drift detection, approval and per-agent grants.

  • Custom HTTP tools

    Available

    Call your own endpoints through the gateway, with encrypted credentials and outbound request protection.

  • Browser game capture

    Available

    Headless Chromium capture of screenshots, video and timings for HTML5 games, with visual regression against approved baselines.

  • Engine bridge registration

    Beta

    Register a Unity, Unreal or Godot bridge as an integration so its tools are approved, granted and audited through the gateway.

    Verified against a simulated engine bridge only; this proves the PWR side of the protocol, not the engine side.

  • Unity, Unreal and Godot editor plugins

    Upcoming

    The editor-side plugins that serve the bridge inside each engine.

    Written but never run inside a real editor; validation on a provisioned engine worker is pending.

Billing

  • Stripe subscriptions and checkout

    Beta

    Plan purchase and subscription lifecycle through Stripe.

    Verified against a simulated Stripe; live Stripe verification is pending and plan pricing is not final.

  • Credit top-ups

    Beta

    One-off credit packages purchased through Stripe and added to the ledger.

    Verified against a simulated Stripe; live Stripe verification is pending and plan pricing is not final.

  • Stripe webhooks

    Beta

    Payment and subscription events update entitlements and the credit ledger idempotently.

    Verified against a simulated Stripe; live Stripe verification is pending and plan pricing is not final.

Questions

What does beta mean on this page?

The integration is implemented and covered by automated tests, but the external service has only been exercised through an in-repo simulator or partially. It moves to available after verification against the live service.

Which GitHub permissions does PWR need?

PWR uses a GitHub App and mints short-lived installation tokens scoped to a single repository with the narrowest permission set for the operation. The GitHub Issues connector additionally needs the Issues permission on the App.

Do you support GitLab or Bitbucket?

No. GitHub is the only source control integration.

Can I connect an internal tool?

Yes, as an MCP server or a custom HTTP tool. It must be approved and granted to an agent before use. Endpoints on private or internal network addresses are refused by default.

Can PWR create issues in Jira?

No. The connectors import issues and write back comments, transitions, labels and links. Issue creation is not supported.

Is pricing final?

No. The billing system is implemented and tested against a simulated Stripe, and plan pricing has not been finalized.

Read the docs

Related

Put an AI development team on your idea.

Describe what you want to build. PWR plans, builds, tests and reviews it, and you approve each step that matters.

Request early accessSee how PWR works