Skip to main content
Experimental version.This is the latest in-development version of AI-Implement. Features may change without notice and behavior is not guaranteed. Switch to the latest stable version here.
The bd- skills reach your issues and repositories through a pair of connectors: your orchestrator and your ticketing system. You add each one once per account at claude.ai › Customize › Connectors. There is nothing to set up per project. Every skill reads its project mappings from the orchestrator at the start of each session, so a fresh checkout needs no .mcp.json entry and no binding file — signing in with the account that holds the connectors is enough.
This assumes the skills are already installed. If not, start with installation first.

​
Connect your services

1

Allow the claude.ai callback origin on your orchestrator

Before a custom connector can authenticate, the orchestrator has to allow the claude.ai callback origin:
Set this first. A connector rejected with invalid_redirect_uri before the sign-in screen appears is missing this origin.
2

Add the connectors

Open claude.ai › Customize › Connectors. Add one connector for each service:
  • your orchestrator — the AI-Implement service that holds your project mappings and picks up marked issues to open pull requests. Click Add › Add custom connector and enter its MCP address: the orchestrator’s base URL followed by /mcp.
  • your ticketing system — Linear or Jira, where your issues live. Find it on the Discover tab and click Connect.
Add each one once per account, from the web. Connectors are added and removed from the web, and enabled or disabled per session from the mobile app.
3

Sign in to Claude Code

The connectors load automatically in Claude Code when you sign in with the same account.No project .mcp.json entry is needed.
At the start of a session, the skills print:
  • the orchestrator they resolved
  • the project binding they read
  • the tracker they checked
Setup is complete once those lines name your services.

​
One tracker connector, one workspace

A tracker connector is signed into one workspace at a time. When a repository’s mapping expects a different workspace, the session-start check names the connector to reconnect to. To work in another workspace, reconnect the tracker connector to it rather than editing any project file.
Linear is supported across the whole suite. Jira works, but some skills describe it in terms projected from their Linear behavior rather than fully adapted — see ticketing support for which.

​
Switch to a different orchestrator, workspace, or project

Use these steps to point the skills at another orchestrator, another Linear workspace, or another project. You change connectors and orchestrator mappings only. No file in your repository changes.

​
Switch the orchestrator

1

Get access on the new orchestrator

Ask an admin of that orchestrator to add your email to its allowlist, in the admin UI Access panel. The user role is enough for the skills. bd-kg-refresh and bd-mega-kg-refresh need the admin role. See Single sign-on.The orchestrator must also allow the claude.ai callback origin (MCP_ALLOWED_REDIRECT_ORIGINS), as in Connect your services.
2

Add the new orchestrator as a connector

Open claude.ai › Customize › Connectors and click Add › Add custom connector. Use the orchestrator’s MCP address, which is its base URL followed by /mcp, for example https://ai-implement-testing-orchestrator.fly.dev/mcp. Do not use the admin page address (/admin#projects).Sign in when the connector asks. Use the account that is on the allowlist.
3

Keep only one orchestrator enabled

Disable the connector for the old orchestrator, or remove it. In Claude Code, run /mcp and disable the old one there too.If two are enabled, each skill stops with this line:
4

Check the session-start lines

Start a new session and run any skill, for example bd-system-questions. The first lines name the new orchestrator:

​
Switch the Linear workspace

1

Reconnect Linear on claude.ai

In claude.ai › Customize › Connectors, disconnect the Linear connector. Connect it again, and choose the new workspace on the Linear consent screen.
2

Reconnect Linear in Claude Code

Run /mcp, select the Linear connector, and choose Reauthenticate. Choose the same workspace.
3

Check the tracker line

Start a new session. The tracker line names the team keys that the orchestrator maps:
If the workspace does not hold those teams, the skill stops with this line. Reconnect to the workspace that holds them:

​
Switch the project

The orchestrator decides which Linear team and which repository go together. Each pair is a project mapping in the admin UI Projects panel, for example https://ai-implement-testing-orchestrator.fly.dev/admin#projects. To use another team or repository, add or change a mapping there. Only an orchestrator admin can do this. A skill that files issues or lands pull requests chooses its project in this order:
  1. A team key or repository that you name in the prompt, such as BDS-87.
  2. In Claude Code, the repository of the folder you work in. In a chat, the optional repo: <owner>/<name> line in the project instructions.
  3. Otherwise, the skill asks you once and lists the mappings.