Your Fluss device is already on the internet. Your AI assistant is already on the internet. Until recently, they couldn't talk to each other without somebody writing custom glue code.

That changed with MCP. This article explains, what MCP is, how to plug the Fluss MCP server into Claude, ChatGPT, or any other LLM you may want to use, and what you can actually do with it once it's connected.

1. What is MCP, in simple terms?

MCP stands for "Model Context Protocol."

Forget the name. Think of it as a USB port for AI assistants.

Before MCP, every AI assistant (ChatGPT, Claude, Grok, Gemini, Copilot, etc.) had its own way of connecting to outside tools. If you wanted ChatGPT to read your calendar and wanted Claude to read the same calendar, somebody had to build the integration twice — once for each assistant.

MCP fixes this. It's a single, open standard that all the major AI assistants now speak. A company builds one MCP server, and every MCP-compatible assistant in the world can use it.

In practice, an MCP server is just a web address (a URL) that exposes a list of "tools" the AI is allowed to call. When you ask the AI to do something, it picks the right tool, calls it, and shows you the result.

That's the whole idea.

2. What is the Fluss MCP server?

The Fluss MCP server lives at:

It's the Fluss platform exposed as a set of tools an AI can use on your behalf. Once you connect it, your AI assistant can:

• List every Fluss device on your account, with the permissions you hold on each one
• Check device status — online/offline, open/closed, firmware version, and WiFi signal strength
• Open a device directly (when it makes sense to use the explicit open command)
• Trigger a device — a state-agnostic command that works regardless of the current open/closed state, useful for gates and intercoms
• Invite a user by mobile number, with Full, Always, Temporary, or Repeat permissions, across one or more devices in a single request
• Revoke a user's access by mobile number (you cannot revoke yourself or the device owner — the same rule that applies in the Fluss app)
• Pull access logs for one or more devices over a chosen time range, with pagination for longer windows

That's seven tools in total. The AI picks the right one for whatever you ask.

It only does what your Fluss account already lets you do. The AI cannot grant itself permissions it doesn't have. If you can't revoke the device owner from the Fluss app, the AI can't either.

3. Installing it

The server URL is the same everywhere — https://mcp.fluss.io. Authentication is OAuth: you click a button, sign into Fluss, approve access, and you're done. No tokens to copy and paste.

Below are the most common AI assistants.

3.1 Claude (claude.ai and Claude Desktop)

1. Open claude.ai (or the Claude Desktop app) and go to Settings → Connectors.
2. Click Add custom connector.
3. Name it "Fluss" and paste the URL: https://mcp.fluss.io
4. Save. Claude will redirect you to the Fluss login page. Sign in with the same account you use in the Fluss app and approve the connection.
5. Start a new chat. The Fluss tools will appear in the connector list at the bottom of the message box.

Note: the Claude connector UI only accepts OAuth-based servers — it won't accept a pasted Bearer token. The Fluss server is OAuth, so just paste the URL above and let Claude handle the rest.

3.2 ChatGPT (OpenAI)

1. In ChatGPT, open Settings and find the Connectors section (available on paid plans — Plus, Pro, Business, and Enterprise).
2. Add a new custom connector.
3. Name it "Fluss" and paste the URL: https://mcp.fluss.io
4. Complete the OAuth sign-in when ChatGPT prompts you.
5. In a chat, enable the Fluss connector for that conversation (the toggle is in the Tools / connectors menu — exact location varies by client version).

3.3 Other MCP-native clients

Cursor, Claude Code, Windsurf, Zed, and similar tools all accept MCP servers. The exact UI differs, but they all need the same single piece of information:

• URL: https://mcp.fluss.io
• Auth: OAuth 2.1

Most of these clients will open the OAuth flow in your browser, prompt you to sign into Fluss, and handle the rest automatically. For terminal-based tools (Claude Code, some Cursor configs), follow the prompts in the terminal — this may involve copying and pasting a generated URL into your browser to complete the OAuth handshake.

3.4 Direct API use

If you're building on top of an LLM API directly (Anthropic Messages API, OpenAI Responses API, etc.), the same URL applies. Refer to the provider's documentation for how to attach a remote MCP server to a request.

4. What it actually feels like to use

Once it's connected, you stop thinking about devices and device IDs. You just talk.

Example conversation

You:

Open the office gate.

The AI:

[calls list_devices, finds "Office Gate", calls trigger_device on its ID] Done — the office gate is opening now.

You:

Did Sarah come in this morning? She was supposed to arrive around 8.

The AI:

[calls get_access_logs for the office gate over the 08:00–09:00 window today] Yes — Sarah's number triggered the office gate at 08:07 this morning.

You:

Give the new contractor — +27 82 555 0143, Mike Daniels — temporary access to the office gate from Monday to Friday next week.

The AI:

[calls give_access with permission "Temporary", start_date and end_date set to next week] Done. Mike has temporary access to the office gate from Monday 09:00 to Friday 17:00 next week.

You:

The contractor finished early. Revoke his access.

The AI:

[calls revoke_access on +27 82 555 0143] Mike's access to the office gate has been revoked.

That's the entire pitch. The AI handles the busywork — finding the right device, picking the right permission type, formatting the dates — and you stay in plain English.

5. A note on safety

Granting an AI assistant the ability to open physical doors is not something to do casually. A few things worth knowing:

• You can disconnect Fluss from any AI assistant at any time, the same way you disconnect any other connector.
• The AI only sees the devices and permissions your Fluss account already has. Connecting it doesn't expand your Fluss permissions.
• Most clients (Claude, ChatGPT, Grok) will ask for confirmation the first time the AI tries to call a tool in a session. You can revoke that confirmation later.
• Every action the AI takes shows up in the same Fluss access logs as a manual action would, with the same audit trail — so you always have a record of what was opened, when, and on whose behalf.
• Because the AI is acting on your behalf, treat your AI assistant account with the same care as your Fluss account. Use a strong password and 2FA on whichever assistant you connect.

6. TL;DR

• MCP is a universal "USB port" for AI assistants.
• Fluss exposes its capabilities at https://mcp.fluss.io.
• Add that URL as a custom connector in Claude, ChatGPT, or any other AI that supports MCP. Sign in once with OAuth. Done.
• Then ask your AI to open or trigger a device, hand out access, pull logs, or check device status — in plain English.

The Fluss app isn't going anywhere. But for everything that used to need three taps and a permission picker, you now have a one-line option: just ask.