Connecting AI assistants

Connect your AI assistant to Bifrost through the Model Context Protocol (MCP) to find projects, check credits, manage builds, upload signing credentials, and run workflows. Sign in with your Bifrost account using OAuth; you do not need to generate or paste a personal token.

Start with your Bifrost account

Create an account on the Bifrost website, using GitHub or email and password. The first onboarding page, Continue with your agent, provides the server URL and a copyable starter prompt. Add the server to your assistant, authenticate with OAuth, and approve access before using any tools.

After connecting, ask your assistant to call get-started. This works before you have a team or subscription. Your assistant guides the next steps; team setup, checkout, and repository approvals still happen in your browser. You can also choose Continue on the website to use the existing onboarding flow.

All MCP requests require authentication, including tool discovery and onboarding. Existing connections that show only “Added” may need their client's Authenticate or Reconnect action before they can run tools.

Before managing a team

The team owner must enable MCP access in the team’s Settings → MCP page. To connect your own assistant, open your account menu, choose Settings, then select the MCP tab. You must be a member of the team, MCP must be available for that team, and the team must have an active subscription. If MCP is not available for your team, contact your team owner or Bifrost support.

Connect with OAuth

In your assistant, add a remote MCP server named Bifrost using the URL below. Choose OAuth if it asks for an authentication method. Your client must support remote HTTP MCP and OAuth discovery.
Connect or authenticate. Your assistant opens Bifrost in a browser so you can sign in and review the requested access.
Approve access and return to your assistant. Ask it to list your Bifrost teams, then choose the team you want to work with.

https://bifrost.nativephp.com/mcp/oauth

When using a preview or another Bifrost environment, copy the Server URL from that environment’s personal Settings → MCP page.

Claude Code

Run this in your terminal:

claude mcp add --transport http bifrost https://bifrost.nativephp.com/mcp/oauth

Then open Claude Code, run /mcp, select Bifrost, and authenticate. Complete the Bifrost sign-in and approval in your browser. See Claude Code's MCP instructions for client configuration details.

Other assistants

Use your client's remote MCP or custom connector settings and enter the same OAuth server URL. Settings names vary by client. Follow its authentication prompt to sign in to Bifrost; do not add a personal-token Authorization header to an OAuth connection.

What your assistant can access

An OAuth connection belongs to you and works across your eligible teams. It can list teams and projects, check credits, create projects, upload signing credentials, start and cancel builds, inspect build status, diagnose failed builds where your plan supports it, and discover, run, and inspect workflows.

This is management access, not a read-only connection. Each platform build uses a team credit. Workflows may start multiple builds and send the emails or webhooks configured by your team. Review the permission screen before approving.

Ask your assistant:

List my Bifrost teams, then show the projects in the team I choose.

The assistant uses list-teams to discover eligible teams and passes the chosen team_id with subsequent tool calls. Choosing a team in the assistant does not change the selected team in your Bifrost dashboard. Access is checked on every request: leaving a team, disabling its MCP access, or losing eligibility prevents further access to that team.

Moving from a legacy personal token

We plan to deprecate legacy MCP personal-token connections. Existing tokens still work, but you should move your assistant to personal OAuth. Users with legacy tokens will see a notice in personal Settings → MCP.

Edit or replace your assistant’s existing Bifrost server configuration.
Change the URL from https://bifrost.nativephp.com/mcp to https://bifrost.nativephp.com/mcp/oauth.
Remove the Authorization: Bearer ... header.
Connect or authenticate again, sign in with your Bifrost account, and approve access.
Ask your assistant to list your teams and choose the team you want to use.

If your client does not support OAuth, use a client that does. Connecting with OAuth does not automatically revoke an existing personal token. No retirement date has been announced here.

Troubleshooting

No sign-in prompt: check that you entered the OAuth URL ending in /mcp/oauth, that your client supports OAuth, and that you used its connect or authenticate action.
An existing connection asks for permission again: reconnect and approve the current management permissions. Older read-only OAuth grants cannot use the expanded tool set.
A team is missing: check membership, the owner's MCP access switch, feature availability, and the team's subscription.

A team owner can turn off MCP access to stop both OAuth and personal-token access to that team.

On this page