mcpbeat Sign in

765T Flow MCP Server

by 765tflow Your server? Claim it
answering

765T Flow is answering right now. Last checked 9 min ago. It exposes 7 tools.

AI for Revit: 450+ tools, 1 undo step. Windows, Revit 2024–2027 (2021–2023 included). Free account.

Uptime history 28 days of history · worst day 99%
28 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
324 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 October 2026. No other catalogue keeps this.

21 Oct a tool changed version2 times that day
and 1 more, back to 21 October 2026

Nothing serious here today

Today is the operative word: we check 765T Flow every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add flow --transport http https://765tflow.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://765tflow.com/mcp
~/.codex/config.toml
[mcp_servers.flow]
url = "https://765tflow.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "flow": {
      "url": "https://765tflow.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "flow": {
      "type": "http",
      "url": "https://765tflow.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

flow
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_tools answers for it, including the reserved members (instanceId always; documentKey where the tool is document-scoped; optional idempotencyKey and dryRun). Read the schema with flow_tools first; names never resolve by similarity.
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 guides; each result lists the tools it leads to. When the catalog has no tool for the job, `answer.kind` is `negative` and `answer.workaround` names the nearest tools and what to do instead. Results are ranked for you to choose from; before you call a tool a result names, read that result with flow_get: a how-to card states what the tool does beyond its schema. `reference` lists up to three sections of curated Revit playbooks on the topic: background to read, ranked by wording only. It never changes `answer.kind`, never lists a tool, and is not proof that the catalog has a tool for the job. Read-only: it never reads or changes a Revit model. Never put project data, model content, file paths or secrets in the query.
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-only.
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; documentKey is required on document-scoped tools only (tools/list names each tool's scope).
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 the arguments by hand.
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 sent — never on your own initiative. The `message` is the report; never include project data, model content, file paths or secrets. The answer returns the `reportId` reference the team tracks the report by.
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 (the schema flow_call's arguments for that tool take, reserved members included) with its document scope, dry-run support and credit class. Names are matched exactly.

Endpoints

URLTransportStateLatencyChecked
https://765tflow.com/mcp streamable-http sign-in 443 ms 9 min ago

Alternatives to 765T Flow

same job, measured the same way
Increase MCP
by mrfentmen

MCP server for Increase: accounts, ACH and wi MCP: real tools for real work.

86 installs/wk local only
Horizun Revit MCP
by horizungroup

Local Windows MCP for Revit 2023-2027. Run the Windows installer before connecting a client.

local only
CSV File Tools
by csvfile

Inspect, filter, sort and edit CSV text with four free tools. No account or API key required.

4 tools answering
BPJ Task Loop
by f-tiger

BPJ rule-based task-state reviews and workflow tool discovery. Free, no account required.

2 tools answering
Agent Einstein — Crypto & Market Intelligence
by emc2ai

AI price forecasts, whale flows, market sentiment and prediction signals. 18 tools free, no account.

40 tools answering
DeskMonitor
by thedeskmonitor

DeskMonitor: 24 workforce-intelligence MCP tools, OAuth 2.1, free demo key included.

24 tools answering
xbrlkit
by robosystems

Read SEC EDGAR and XBRL filings with an AI: 18 tools over the filing itself. Local, free, no account

935 installs/wk local only
Algolia Productivity
by algolia

Connect LLM tools to your Algolia account with user-scoped access for internal workflows.

answering

765T Flow — questions

Answers built from our own checks of this server.

What can 765T Flow do?
It exposes 7 tools, read directly from the server on our last check. Among them: flow_call, flow_find, flow_get, flow_list_instances, flow_read_result, flow_report_issue and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is 765T Flow working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 324 ms. The bar chart above shows every period we have measured.
How do I connect 765T Flow?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to 765T Flow?
No API key is involved. 765T Flow answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is 765T Flow?
It answers our handshake in 324 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.