# Connect Flightplan to Claude

Flightplan can be connected to Claude and other AI assistants. Once connected,
you can ask about your work in plain language and the assistant reads and
updates Flightplan for you:

- "What are my tasks?"
- "Start the new-client onboarding for Acme Corp."
- "Here is our closing procedure -- build a workflow from it."
- "Write up last week's safety walkaround as a PDF."

The assistant sees the same things you see, and can do the same things you can
do. It cannot see another workspace, and it cannot see anything you could not
open yourself.

## Connect it

1. In Claude, open **Settings**, then **Connectors**.
2. Select **Add custom connector**.
3. Enter `https://flightplan.run/mcp` as the URL.
4. Sign in to Flightplan when the browser opens.
5. **Choose your workspace**, then approve the access Flightplan asks for.

Step 5 is the one to read. The workspace you pick is the only workspace that
connection can ever reach.

### If you belong to more than one workspace

One connection reaches one workspace. To work in a second workspace, add a
second connector and pick that workspace when you connect it.

This is deliberate. The workspace is fixed to the connection when you approve
it, so an assistant cannot wander into another one, and nothing you ask it to
do can be answered from the wrong set of workflows.

## What it can do

| Ask for | What happens |
|---|---|
| Your workflows and what is in them | Reads them |
| Your checklists and where each one has got to | Reads them |
| Your tasks, across every running checklist | Reads them |
| Your schedules and when each one next fires | Reads them |
| The full record of a finished checklist | Reads it |
| Starting a checklist | Starts one |
| Completing or skipping a task | Does it, as you |
| Commenting on a task | Posts it, under your name |
| Attaching a file to a task | Shows you a form to pick one |
| Building or changing a workflow | Does it |

Everything it shows you links back to the page in Flightplan, so you can open a
task and finish it there instead.

### Filling in a task

A task can ask for information before it closes. You can answer in the
conversation and the assistant fills the fields in for you.

When a task collects a file, the assistant shows you the form instead. Pick the
file, fill in the rest, and close the task from there. It is recorded exactly as
it would be on the page -- as closed by you, with the file kept as evidence.

Files attached this way are limited to 4 MB. For anything larger, open the task
in Flightplan and attach it there.

This form needs an assistant that can display one. Claude and Claude Desktop
can. If yours cannot, it says so, and the task is still yours to close on the
page.

### Read-only access

On the approval screen you can grant reading without granting changes. A
read-only connection can answer questions and write documents, and cannot start
a checklist, close a task or edit a workflow.

## Documents, reports and PDFs

Ask the assistant for the document and it writes it. Flightplan hands over the
complete record of a checklist -- every task, who closed it and when, every
answer it collected, every [comment](comments.md) left along the way,
everything attached as evidence, and the full activity feed -- and the
assistant turns that into whatever you asked for.

A finished [checklist summary](checklist-summary.md) is the usual source. Ask
for an incident write-up, a handover note, a compliance record or a slide, and
say what you want it to emphasize.

## Building a workflow from a document

Paste a procedure, or point the assistant at a document, and ask for a workflow.
It decides what the tasks are, what order they run in, and which ones can happen
at the same time, then builds it.

What arrives is a **draft**, laid out on the canvas and ready to look at. Open
it in the builder before you publish it:

- Tasks arrive unassigned. Assign them yourself -- see
  [How assignment works](assignment.md).
- Check the [prerequisites](prerequisites.md). The order it chose is a
  reading of your document, and only you know if it is right.
- Add any [fields](fields.md) that a task should record.

Nothing runs until you publish it.

## What it does not touch

**Automations stay as they are.** If a task posts to Slack or calls a webhook,
an assistant editing that workflow leaves the automation exactly as you
configured it. There is no way to add, change or remove one over a connection.

**Running checklists stay frozen.** Editing a workflow never changes a checklist
already in flight, whoever does the editing.

**Your name goes on your work.** A task the assistant closes is recorded as
closed by you, because you asked for it. It appears that way in the checklist's
history like any other completion.

## Disconnect it

Remove the connector in Claude. Access stops, and nothing in your workspace
changes.

Losing access to a workspace also ends the connection. If somebody is removed
from a workspace, their connector stops working there within a few minutes,
even though they approved it earlier.

## Other assistants

Any tool that supports remote MCP servers can connect to the same URL,
`https://flightplan.run/mcp`, and will ask you to sign in the same way.

Every connector acts for a person who signed in. For a machine that has no
person behind it -- a build pipeline, a scheduled script -- point a task at a
[webhook](connections.md) and let the callback token in the payload close the
task.