# 765tflow Flow MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.765tflow%2Fflow
Registry id: `mcp-registry/com.765tflow/flow`
Status: auth-required (checked 2026-10-26T17:10:51.862Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 263
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "765tflow-flow-mcp-server": {
      "type": "http",
      "url": "https://765tflow.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http 765tflow-flow-mcp-server https://765tflow.com/mcp
```

## Tools (7)

- `flow_call`: Execute one 765T Flow catalog tool by its exact name. `arguments` is exactly the arguments a direct call to that tool carries — the advertised input schema flow
- `flow_find`: Find the right 765T Flow tool, or the how-to, for a Revit job. Describe the job in plain words, in English or Vietnamese. The answer ranks tools and short guide
- `flow_get`: Read one guide, tool entry or playbook section in full, by the `ref` flow_find returned for it. Pass the ref exactly as returned; never form one by hand. Read-o
- `flow_list_instances`: List this account's connected Revit instances and their open documents. The instanceId it returns is the reserved member every catalog tools/call requires; docu
- `flow_read_result`: Read one part of a call's tools/call answer — call it exactly the way a parted answer's `next` member names it: {callId, part, textSha256} verbatim. Never form 
- `flow_report_issue`: Report a bug, feedback or a feature request to the 765T Flow team. Call this tool only when the user asks you to report something or agrees a report should be s
- `flow_tools`: The 765T Flow catalog door. Call it with no arguments for the tool groups; with {group} for one group's members; with {tool} for one tool's exact input schema (

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.