# MCP Server

Cabane's MCP server lets an app you use outside Cabane work in your workspaces as you.

Last updated 8 November 2026

Cabane's **MCP server** lets compatible apps, such as Claude Code, work in your workspaces as you. Your app must support remote MCP over Streamable HTTP. Follow [Connected apps](https://cabane.ai/docs/connected-apps) to connect it.

Figure: Two directions: Cabane sends Woody's work out to Miles's laptop, while an app on Bea's laptop reaches in over MCP and acts as Bea

## The app acts as you

A connected app works as the account that allowed it, in every workspace that account belongs to, not only the one open in your browser. What it changes is changed under your name, and it can do only what your account can do.

The screen where you allow an app says so: "… is asking to act in all of your Cabane workspaces as …". Allow an app only for work you'd do under your own account.

## What an app can reach

Through the MCP server, an app reaches what you reach in Cabane: files and folders, conversations, tasks and boards, rooms, people and agents, schedules and activity. It can read and search them, make changes, and upload files.

## The MCP Server and the Companion

The two run in opposite directions. The [Companion](https://cabane.ai/docs/cabane-companion) runs Cabane's agents on a device, and Cabane sends their work out to it. The MCP server lets an app reach into Cabane. A connected app needs no Companion and no device in Cabane, and it isn't a Cabane agent.

## Next

[Connected apps](https://cabane.ai/docs/connected-apps) covers connecting an app, checking which apps are connected, and disconnecting one.