# 765T Flow

> AI for Autodesk Revit on Windows 10 or 11 (463 catalog tools the hub serves across 15 groups). Works with Revit 2024–2027. Revit 2022 and 2023 are included but not yet tested in a live Revit session. Every write lands inside one named undo step in Revit: one Ctrl+Z takes the whole write back. FLOW does not charge a fee during Early Access.

## What 765T Flow is

- No cloud builds your model for you. FLOW runs through a hosted endpoint and a connector on your machine, shows what a change would do when the call asks for a preview, and reports the result and the elements it changed afterwards.
- The assistant never talks to Revit directly. Between your prompt and the open model, the request goes through 765tflow.com/mcp and the FLOW add-in for Revit: every Revit API call runs inside the Revit process on your machine.
1. The assistant you use: Sends a request over MCP to 765tflow.com/mcp. It does not know the Revit API, only the list of tools FLOW lets it see.
2. The 765tflow.com/mcp endpoint: 765tflow.com/mcp authenticates your signed-in account, checks the call against the declared tool surface, and sends the signed command down the live connection your Revit session opened.
3. The FLOW add-in for Revit: Receives the signed command on the outbound connection it opened, verifies the signature, and queues the work for a valid Revit API thread.
4. Your open Revit model: The add-in reads or edits the model on your machine; each write commits inside one named undo step (Ctrl+Z), and the RVT file never leaves your computer.
- Preview is optional: for a tool that supports a dry run, the call sets dryRun to check first without touching the model.
- Every write lands inside one named undo step in Revit: one Ctrl+Z takes the whole write back.
- After the write, the tool reports the execution result and the list of elements it changed.
- A write whose outcome is uncertain is never blindly retried.

## Public pages

- https://765tflow.com/ — AI for Revit, working with you
- https://765tflow.com/how-it-works — 765T Flow — How it works: The path a request takes through 765T Flow: four hops from your AI app to the model, an optional dry-run preview before a write, one tool surface declared per tool, and a result report after execution.
- https://765tflow.com/docs — Install 765T Flow for Revit: Install 765T Flow for Revit on Windows: the MCP endpoint, its seven hub tools, how each write lands as one undo step (Ctrl+Z), and how to connect Codex, Claude, Cursor, Antigravity or Devin.
- https://765tflow.com/download — Windows installer download instructions and SmartScreen steps
- https://765tflow.com/releases — Release notes for published builds
- https://765tflow.com/support — Support, troubleshooting, and contact (mailto:contact@765tflow.com)
- https://765tflow.com/community — Public community discussions and guides
- https://765tflow.com/privacy — Privacy policy
- https://765tflow.com/terms — Terms of Use

## MCP endpoint

- URL: https://765tflow.com/mcp
- Transport: streamable HTTP
- Authentication is OAuth 2.1 with PKCE in the browser: the first connect opens a 765T Flow page and you click "Authorize" once. No API key or token sits in a configuration file.

## Seven hub tools (tools/list)

- flow_list_instances: Lists the account's connected Revit instances and their open documents, and returns the instanceId every catalog call needs.
- flow_read_result: Reads the next part of a long answer, exactly as that answer's next pointer names it.
- flow_report_issue: Sends a bug report, feedback or a feature request to the 765T Flow team when you ask for it, and returns a reference id.
- flow_tools: Browses the catalog: the tool groups, one group's members, or one tool's exact input schema.
- flow_call: Runs one catalog tool by its exact name, with arguments in the schema the catalog browse step returned.
- flow_find: Finds the right tool or how-to guide for a Revit job described in plain words. Read-only.
- flow_get: Reads one guide or tool entry in full, by the ref the search step returned. Read-only.

## How to connect

### 1. Install Control Center on Windows
- The installer sets up Control Center and the add-in for Revit for your Windows user only, and no administrator rights are needed. Works with Revit 2024–2027. Revit 2022 and 2023 are included but not yet tested in a live Revit session.
1. Create a free account or sign in with Google or email on 765tflow.com, then click Download for Windows in your account. If your browser blocks the downloaded file: in Chrome, open Downloads and choose Keep; in Edge, hover the download, click the three dots → Keep → Show more → Keep anyway.
2. Run the installer. When you open the installer, Windows may show a blue “Windows protected your PC” screen. FLOW is new, and its installer is not code-signed yet. Windows shows it for any app it has not seen often yet. Click More info. The screen says Publisher: Unknown publisher. Click Run anyway. The installer then opens as usual. Button names follow your Windows language.
3. Open Revit. When Revit asks about the 765T Flow add-in, choose Always Load.
4. Optional, and it clears the block your browser attached to the file: right-click the downloaded .exe → Properties → General tab → tick Unblock → Apply.
5. No Run anyway button at all? Smart App Control is blocking the installer, and Windows has no way to allow this one app through. Install it on this PC, where Revit runs. You can turn Smart App Control off in Windows Security to install. FLOW's files are not code-signed, so with Smart App Control on, Windows can block FLOW itself, not only the installer. Keep it off while you use FLOW. Windows may ask for an administrator's permission to change it, so if your company manages this PC, ask your IT first.

Then pair the Revit side with your account:
1. Open 765T Flow Control Center.
2. Press "Sign in" on the account strip.
3. The browser opens this very site: click "Authorize" once. The card updates itself when the account is accepted.

### 2. Connect Claude
1. In Claude (on the web or in the desktop app), open "Customize > Connectors".
2. Click "+", then "Add custom connector", and paste this address:
3. Click "Add": the browser asks for "Authorize" once, and that is all it asks.
  https://765tflow.com/mcp

### 3. Connect Cursor
- With Cursor installed, click the button below. Cursor asks you to confirm, then adds the 765t-flow server.
- One-click install link: cursor://anysphere.cursor-deeplink/mcp/install?name=765t-flow&config=eyJ1cmwiOiJodHRwczovLzc2NXRmbG93LmNvbS9tY3AifQ==
- Or add this block to ~/.cursor/mcp.json yourself, then restart Cursor:
{
  "mcpServers": {
    "765t-flow": {
      "url": "https://765tflow.com/mcp"
    }
  }
}

### 4. Connect Antigravity
- Antigravity reads remote MCP servers from the serverUrl field in its raw MCP configuration (mcp_config.json):
- Official docs: https://antigravity.google/docs/mcp
1. Open mcp_config.json from the Antigravity IDE Agent side panel (… menu → MCP Servers → Manage MCP Servers → View raw config) or edit ~/.gemini/config/mcp_config.json directly.
2. Add the 765t-flow server entry under mcpServers and save the file:
3. Open Agent settings (Ctrl+, on Windows) → the Customizations tab, click Authenticate next to 765t-flow, and click "Authorize" in the browser.
4. After you click "Authorize", the browser lands on Antigravity's callback page (antigravity.google/oauth-callback) and shows a one-time OAuth authorization code. Copy that authorization code, paste it back into the Antigravity settings panel, and click Submit so the app on your PC receives the code from the browser and finishes connecting 765t-flow.
{
  "mcpServers": {
    "765t-flow": {
      "serverUrl": "https://765tflow.com/mcp"
    }
  }
}

### 5. Connect Codex
- Codex stores a remote MCP server in ~/.codex/config.toml, under [mcp_servers.765t-flow]. Add this block:
[mcp_servers.765t-flow]
url = "https://765tflow.com/mcp"
- Then run codex mcp login 765t-flow. The Codex CLI and the Codex IDE extension read this same file.
- Official docs: https://developers.openai.com/codex/mcp

### 6. Connect Devin
- On the Devin CLI, add the remote server for your Windows user:
devin mcp add -s user 765t-flow https://765tflow.com/mcp
- That command writes the user file %APPDATA%\devin\mcp_config.json. The url field is the one the CLI documents for a remote server:
{
  "mcpServers": {
    "765t-flow": {
      "url": "https://765tflow.com/mcp"
    }
  }
}
- Then run devin mcp login 765t-flow.
- Official docs: https://docs.devin.ai/cli/extensibility/mcp/configuration

Other apps with remote MCP over streamable HTTP and OAuth use this same address. 765T Flow writes nothing to any app's configuration on its own, and the Add to Cursor button adds the entry only when you confirm in Cursor.