# Connect Inflight to your agent

Use the remote MCP server at https://mcp.inflight.co/mcp. Include the /mcp path; the bare domain is not the OAuth resource. Native MCP uses browser authorization, not the legacy Inflight CLI API key.

## Explain the session restart before setup

Before setup, tell me that browser approval connects my account, but this running chat may need a restart to load the newly added Inflight tools. Explain this as an expected setup step: some agent clients load MCP tools when a session starts. Do not imply that every MCP client always requires a restart.

After approval, check whether Inflight's tools are available to this session (including tool discovery, if supported). If available, verify with the read-only list_projects call and continue. If configuration and sign-in succeeded but the tools are still unavailable, pause before sharing and lead with: "Inflight is installed and you've signed in. The remaining step is to restart your agent session so it can load the new tools." Only claim the installation or sign-in succeeded when confirmed. Missing tools alone do not mean authentication failed: do not reinstall, repeat login, or try to bypass the missing tools with raw API calls. Investigate an actual authentication or connection error separately.

Give the restart action for the client I'm using: for Codex CLI, exit and relaunch Codex in the same project; for a desktop or editor client, use its MCP reload/restart control if available, otherwise restart the client and start a new chat in the same project. Save any work needed for the next session and give me a paste-ready continuation containing the original task, remaining setup steps, and exact saved file paths or preview URL. It should first call list_projects, then resume the task without repeating completed setup. Do not assume a new chat remembers this conversation. When pausing for a restart, end with "Restart required; verification pending" rather than calling setup complete.

## Claude

In the Customize page, open Connectors and choose Add custom connector:

```
https://mcp.inflight.co/mcp
```

Click Connect on the new connector and approve in the browser. The connector works in both Claude Desktop and Claude Design.

## Claude Code

Run this in your terminal:

```
claude mcp add \
  --scope user \
  --transport http \
  inflight https://mcp.inflight.co/mcp
```

Run /mcp in Claude Code, choose inflight, and approve in the browser. Start a new session if the current chat has not loaded the tools.

## Codex

Run this in your terminal:

```
codex mcp add inflight --url https://mcp.inflight.co/mcp
```

Approve the connection in the browser. If sign-in doesn't open, run codex mcp login inflight. If this chat hasn't loaded Inflight's tools, restart the Codex session. Signing in connects your account; restarting lets the session load the new tools.

## Cursor

Paste this into Cursor's agent:

```
Add the Inflight MCP server to ~/.cursor/mcp.json:
an "inflight" entry with url https://mcp.inflight.co/mcp.
Keep any servers already in the file.
```

Cursor picks up the server and prompts you to log in. Approve it in the browser, then start a new chat to load the tools.

## Existing installations and recovery

Inspect the configuration this agent actually uses before adding another server. Reuse a working connection. If an Inflight entry points to the bare domain, correct it to https://mcp.inflight.co/mcp and authenticate that connection. Updating a plugin requires updating its published configuration; editing a local cache is not a durable fix.

Older Inflight plugins require retired tools such as inflight_get_workspaces, inflight_list_workspaces, and inflight_create_version. Missing retired tools do not mean authorization failed. Update or disable the obsolete plugin workflow and use the current tools below. Do not repeatedly ask the user to sign in to satisfy a retired tool name.

Do not report setup complete until a real tool call succeeds. If tools remain unavailable after restarting, inspect the active client's configuration and connection errors before changing setup or asking for another sign-in.

For a hosted chat client that cannot run terminal commands or edit project files, guide the user through that client's remote MCP connection settings using the same URL. Do not run commands for a different agent or claim to configure a client you cannot access.

## Share and retrieve feedback

Use share_html for standalone HTML prototypes; no repository or GitHub connection is required. Pass the complete HTML for small files, or follow the returned upload command for larger files. If needs_workspace is returned, ask the user to choose from the returned workspaces.

Use share_preview for a deployed application. It needs the Inflight widget tag committed in the app's HTML head on the commit being shared: find it with git grep -n inflight.co/widget.js HEAD and pass tag_file (its repo-relative path) and tag_org (the data-org value as the file has it) along with repo, full HEAD sha, and branch from the checkout. Derive title, overview, note, questions, and starting_route from the work (omit note and questions when the user gave no ask, and starting_route when unsure of the page). A tag_required result hands you the exact tag and where it goes: insert it, commit only that file on the current branch with a pathspec commit (git commit -m "Add Inflight widget tag" -- that file; never git add -A or commit -a, so nothing the user already staged rides along), push, and call again with the new HEAD sha. If that file already had the user's own uncommitted edits, stop and ask them before committing. tag_mismatch likewise means nothing was shared; do what its next says and call again. url_needed lists how to find this platform's preview URL. Only a result whose status is shared carries the link: give the user its url and relay its say word for word. The page's data-org tag selects the workspace: preserve it and ask for a choice only when the tool requires one. Commit on the branch the repo works on, main itself when the repo only ships from main. A provider-owned production URL (*.vercel.app and the like) is fine to share; when the tool answers production_domain for a custom domain, ask the user before sharing it. A shared preview keeps its deployment URL; /p/ links are for hosted HTML.

Every share is published into a project on the spot. Inflight does not read the page (most previews sit behind a sign-in wall), so the share rests on the tag you attested: tell the user to open the link once and expect the widget at the bottom right.

When asked for feedback, use get_feedback with the shared URL, repo plus sha/branch, or no arguments for recent work with feedback. Use complete_next_step as each selected next step is completed.

## Remember this workflow

For agents with project-file access, add these sharing and feedback instructions to the instruction file the agent actually uses (AGENTS.md, CLAUDE.md, or its equivalent). Preserve existing instructions and avoid duplicates. Explain any remaining authentication, session restart, widget edit, or preview deployment before calling setup complete.