Skip to content
DutopilotDutopilot

Connect Claude to Dutopilot

· 4 min read

Connect Claude to your Dutopilot projects and you can check status, file tickets and act on them without leaving your chat. It runs over MCP, an open standard for connecting assistants to tools, and takes about two minutes.

An AI chat window linked by a cable to a Dutopilot project board with columns of ticket cards.
Your assistant on one side, your Dutopilot project board on the other.

Connect in the Claude app

These steps work on the Free, Pro and Max plans.

  1. In Claude, open Plugins in the left sidebar.
  2. Click Add, then Add custom connector.
    The Add menu on the Claude Plugins page with the Add custom connector option.
    The Add menu on the Plugins page.
  3. Name it Dutopilot, paste https://app.dutopilot.com/mcp as the MCP server URL, and click Continue.
    The Add custom connector dialog in Claude, filled in with the name Dutopilot and the MCP server URL.
    The dialog, filled in with Dutopilot and the URL.
  4. Claude opens the Dutopilot sign-in page. Click Send me a code, enter the 6-digit code from your email, and allow access.
    The Dutopilot page that asks you to allow Claude access, with a box for the 6-digit code.
    The Dutopilot page that asks you to allow Claude.
  5. Back in Claude, Dutopilot shows as Connected on its plugin page.
    The Dutopilot plugin page in Claude showing the status Connected.
    Dutopilot shows as Connected.

Free plans allow one custom connector.

Three steps: add the connector, sign in with a code, then use it in a chat.
Add the connector, sign in with a code, then use it in a chat.

On a Team or Enterprise plan

An Owner adds the connector once for everyone. Open Organization settings, then Connectors, click Add, then Custom, then Web, and use the same name and URL.

Each member then opens Plugins in Claude, finds Dutopilot, connects it, and signs in with their own email code.

Turn it on in a chat

Click the + in the message box, choose Plugins, and switch Dutopilot on. Tool access in the same menu lets you choose which tools Claude may use.

The + menu in a Claude chat with Plugins open and Dutopilot switched on.
The + menu with Dutopilot switched on.

Desktop and mobile

Once you add the connector on the web, it also works in the Claude desktop and mobile apps. There is nothing extra to set up.

Connect in Claude Code

In Claude Code, one command adds the connector:

claude mcp add --transport http dutopilot https://app.dutopilot.com/mcp

Then run /mcp in Claude Code, choose dutopilot and sign in with the emailed code.

The tools, in plain words

The connector has seven tools, in two groups. The two admin-only tools are marked.

Only read

These look at your work and never change it.

  • statusRead your projects, a project board or a single ticket.
  • get_settingsRead project settings.
  • branch_testsRead which tests fail on the default branch.

Change things

These change your project, so they follow your role.

  • file_ticketCreate a ticket on your project board.
  • actTake an action a ticket offers, like approve the plan, stop or resume.
  • update_settingsAdmins onlyChange settings and AI accounts, and check that an AI account works.
  • seo_content_runAdmins onlyQueue an SEO content job.

Claude groups the tools the same way, as read-only and write/delete. On the connector's Permissions tab you choose, per tool, whether Claude asks you first.

The Permissions tab in Claude listing the read-only Dutopilot tools.
Claude's Permissions tab for Dutopilot's read-only tools.

Everyone on a Dutopilot project can connect and use the read tools. Filing a ticket needs at least the Member role, the actions a ticket offers depend on your role, and two tools are admin-only; they are marked above.

Your chat history stays yours

The server cannot read your chat history. It receives only what the assistant puts into a tool call, such as the text of a ticket you ask it to file. The rest of your conversation stays between you and the assistant. The privacy page has the details.

Disconnecting

You can disconnect at any time from the connector settings of your assistant. A connection that sits idle expires after 7 days.

Questions and help

Anything unclear, or something that does not work, write to [email protected].

Let's work smarter, not harder

Put Autopilot on a slice of your backlog.

Book a call and we will scope a pilot on one project, or start free with the Solo plan.