Use Bowtie One with your AI assistant

Connect your assistant

If Bowtie One is listed in your assistant's directory of connectors or apps, add it from there. If it is not, add it as a custom connector with the server address above. Either way you are sent to Bowtie One to sign in and approve the connection; there is no key to copy.

Claude (claude.ai, Claude Desktop, Claude mobile)

1. Open Settings, then Connectors.
2. Find Bowtie One in the directory, or choose Add custom connector and paste the server address.
3. Select Connect, sign in to Bowtie One, choose what Claude may do, and select Approve.

On Team and Enterprise plans an owner may need to add the connector for the organisation first.

ChatGPT

1. Open Settings, then Apps (called Connectors on some plans).
2. Find Bowtie One, or, with developer mode switched on, create a connector with the server address and OAuth sign-in.
3. Select Connect, sign in to Bowtie One and approve.

Claude Code

claude mcp add --transport http bowtie-one https://app.bowtie.one/api/mcp

Then run /mcp inside Claude Code and choose Bowtie One to sign in. Your browser opens the Bowtie One approval page; the sign-in comes back to Claude Code on your own computer.

Cursor

Add this to your Cursor MCP settings (mcp.json), then select Connect next to Bowtie One:

{
  "mcpServers": {
    "bowtie-one": { "url": "https://app.bowtie.one/api/mcp" }
  }
}

Grok

If Bowtie One is in Grok's plugin marketplace, add it there and sign in. To use it through the xAI API, use an access key (below) as the authorization for the remote MCP server at the server address.

Anything else: access keys

Some tools cannot sign in through a browser. For those, create an access key on your account page under Connect an AI assistant. A key is shown once, can be read-only or read-and-edit, can expire, and can be revoked at any time. Send it as Authorization: Bearer followed by the key.

What your assistant can do

• List your bowties and open any of them in full: the hazard, the unwanted event, every threat, consequence, barrier and escalation factor.
• Review a bowtie's risk with the same scoring the builder uses: the worst pathways, and the gaps that need action, worst first.
• Explain the method: how a bowtie is built here, the likelihood and severity scales, the barrier types and what each gap means.
• Create a new bowtie from a conversation.
• Add to a bowtie: threats, consequences, barriers, escalation factors and their controls.
• Edit a bowtie: rename, move or remove items, or switch it between Work as imagined and Work as done. A large removal needs an explicit confirmation.

It works only with bowties your account can open, and it can only change the ones you can edit. A bowtie shared with you as a viewer stays read-only. Every reply that changes a board includes a link to open it in the builder.

Nothing is lost. Before an assistant first changes a board, Bowtie One keeps the board as it stood, and each change is saved in the board's version history, marked as changed by an AI assistant. You can restore an earlier version from your dashboard.

What it cannot do

• Delete a bowtie.
• Share a bowtie, invite people, or change who can see it.
• Restore, export or download versions.
• Change your account, membership or billing.
• Answer “Could more be done?” on your behalf. That is a person's sign-off.
• Mark a barrier as checked and working without a verification date or a pass. It is stored as not yet checked, and the assistant is told why.

Read only, or read and edit

When you approve a connection you choose Read and edit or Read only. A read-only connection can list, open and review your bowties but cannot create or change anything, and the assistant is not offered the tools that would. To change your mind, disconnect it and connect again.

Disconnect

Your account page lists every connected app under Connected apps, with what it may do and when it was last used. Disconnect stops it working with Bowtie One at once, including any sign-in the assistant kept. Removing Bowtie One inside your assistant stops that assistant using it; disconnect here as well to be certain. Access keys are revoked from the same page.

A connection that is not used for 90 days expires, and the assistant asks you to sign in again.

Things to ask

• “List my bowties.”
• “Which pathways on my Excavation bowtie are the worst, and what would bring them down?”
• “Build a bowtie for working at height on a mobile tower scaffold. Ask me questions first.”
• “Add a barrier to the trench collapse threat: a competent person inspects the shoring before each shift.”
• “Explain the likelihood and severity scales you are using.”

Your data

When your assistant reads a bowtie, what it reads is sent to the company that runs the assistant (Anthropic, OpenAI, xAI, Cursor or whoever you chose) and handled under your agreement with them. Bowtie One does not send your bowties to any AI provider itself, and does not use them to train anything.

For each connection Bowtie One keeps the app's name and website, what you allowed it to do, and when it was connected and last used. Sign-in tokens are stored only in a form that cannot be turned back into the token. A security log of connections, sign-ins and changes is kept for 12 months. It records what happened and when, never the content of your boards.

The Privacy Policy and Terms of Use cover this in full.

If something goes wrong