MCP servers
Give the agent extra tools by connecting Model Context Protocol servers.
The agent has a solid built-in toolset, but you can extend it. Clusy supports MCP, the Model Context Protocol, which is an open standard for exposing tools to an AI. Connect an MCP server and its tools become things the agent can call, alongside its built-in ones.
What it's for
MCP is how you teach the agent to do things specific to your world: query an internal warehouse, hit a private API, or reach a service that isn't built into Clusy. If there's an MCP server for it (and there are many, plus you can write your own), the agent can use it.
Adding a server
Manage servers under Settings → MCP servers. A server uses one of two transports:
- Streamable HTTP: a hosted server you reach by URL, with optional auth headers.
- stdio: a command-based server, where you give the command, arguments, environment variables, and working directory.
Once added, you can enable or disable a server without deleting it, and edit it later.
Approving tools
Connecting a server doesn't hand the agent a blank check. Each server exposes a set of tools, and you approve the ones the agent is allowed to use. You see the tools, and you decide which are in play.
Review before you approve
An MCP tool can reach outside Clusy, into your systems, with your credentials. Approve the ones you understand and trust, the way you'd think about granting an app a permission. You can revoke approval or disable the server any time.