Back to the blog

An MCP server for Nextcloud: what exists, and what Bee Flow offers

· By Bee Flow · 4 min read

Three ways to give a desktop or editor AI client Nextcloud tools over MCP: Context Agent's own server, a community project, and Bee Flow's /mcp endpoint. What each needs, and why Bee Flow is not a standalone Nextcloud MCP server.

A hub with cables running to a calendar, a folder and an envelope

Someone who searches for a Nextcloud MCP server usually wants an AI client on their desktop or in their editor to read and change things in Nextcloud. Claude Desktop, Claude Code, Cursor and many others speak the Model Context Protocol, so what they need is a server that offers Nextcloud as MCP tools. There are three ways to get that today. Bee Flow is one of them, with a catch. You need a Bee Flow server, and the Nextcloud tools come with it. Bee Flow is not a standalone Nextcloud MCP server.

Nextcloud's own: Context Agent

Context Agent, the app behind the Assistant's agent features, also exposes its tools as an MCP server. Its documentation gives the endpoint as

https://your-nextcloud-domain.com/index.php/apps/app_api/proxy/context_agent/mcp/

with a Nextcloud app password sent as the bearer token, so each user connects with their own. Context Agent is an ExApp and needs AppAPI 3.1.0 or later with a deploy daemon. Its tools cover Calendar, Tasks, Contacts, Files, Talk, Mail, Deck, Forms, Share and Tables.

A community server

nextcloud-mcp-server is a separate project on a personal GitHub account, licensed AGPL-3.0. It runs outside Nextcloud, through uvx, a Docker image or a Helm chart, and speaks streamable HTTP or stdio. Its README lists tools for Notes, Calendar, Contacts, Files, Deck, Cookbook, Tables, Sharing, News, Mail, Collectives, Talk and Shopping List. It signs in with app passwords, or for several users through Nextcloud's Login Flow v2.

What Bee Flow has

Bee Flow is an MCP client first. Chats and agents can use tools from any MCP server, the two above included, and connecting MCP servers to a team workspace explains who may add one. Bee Flow also has its own Nextcloud tools for Files, Calendar, Contacts, Mail, Talk, Deck, Tasks, Notes, Tables, Forms, Activity, Notifications and user status, offered when the app is installed in your Nextcloud. Through the connector they run under the user's own Nextcloud account. Without the connector, Bee Flow reaches Nextcloud per user with OAuth or an app password. The other services you can connect are on integrations.

Every Bee Flow server is also an MCP server, at /mcp. An outside client connects there with a personal token, and its tool list is what that user can use in Bee Flow chat: the Nextcloud tools once they have Nextcloud connected, their other integrations (Google, Microsoft 365 and so on), data tables, and automations they published as agent-callable. The list is resolved again on every call, so switching off an integration for someone takes effect straight away.

That gives a desktop client Nextcloud tools, but only by way of a Bee Flow server. If Nextcloud in your AI client is all you want, the two options above involve less to run.

Context Agent nextcloud-mcp-server Bee Flow /mcp
Runs As an ExApp in Nextcloud Next to Nextcloud In the Bee Flow server
Credential Nextcloud app password App password or Login Flow v2 Bee Flow MCP token
Tools Nextcloud apps Nextcloud apps Nextcloud apps plus the user's other Bee Flow integrations
Needs besides Nextcloud AppAPI with a deploy daemon A host for the server A Bee Flow stack

Connecting a client to Bee Flow

In Bee Flow, open Settings and create a token under MCP tokens. You give it a name, switch on the Integrations server at level read (read-only tools only) or write, and can limit it to named tools, a list of IP ranges or an expiry date. The token is shown once. The page then offers a ready command for Claude Code:

claude mcp add --transport http beeflow https://bee.example.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Any client that speaks streamable HTTP connects the same way. The endpoint answers a single POST with JSON-RPC and does not open an SSE stream. It supports initialize, tools/list, tools/call and ping. Each tool carries readOnlyHint and destructiveHint annotations, taken from the same classification our automation dry runs use. A tool that has not been classified counts as one that changes data, so a client that asks before writes will ask.

Organisation admins set one policy for all MCP access under Organisation → Security → MCP access. They can switch it off, allow it only from given IP ranges, limit it to certain roles or users, and refuse older tokens that cannot be scoped. Each token is limited to 120 requests per minute, and each user to 300 across all their tokens. Creating and revoking tokens goes into the audit log. The MCP docs have the details, including how IP lists depend on the reverse proxy.

The other way round

Context Agent can also use Bee Flow as one of its remote MCP servers, which puts Bee Flow's tools inside Nextcloud's Assistant. Nextcloud Assistant and Bee Flow covers how the two run side by side. The token you enter there is used for every user, so that service acts as the person who created the token. Our Nextcloud install docs show the configuration.

Trying it

The /mcp endpoint is part of every Bee Flow server, whether you host it yourself or run it in our EU cloud. AI for Nextcloud shows what your users get inside Nextcloud, and installing Bee Flow next to Nextcloud goes from an empty Docker host to a paired connector. If you want to know whether it fits the clients your team uses, contact us.

#nextcloud #security