Your desktop apps, and your own MCP servers

Two changes let Bearly work with tools it could not reach before. In the desktop app, Computer Use can look at your screen and operate the applications you already have open. And Connectors now accepts any MCP server you point it at, not only the fifteen services in Bearly's built-in list.

Both ask before they act, and neither does anything in a conversation until you say so.

Bearly can operate the apps on your screen

Computer Use is not a mode you switch on. Describe a desktop task in an ordinary message, and Bearly asks for access when it needs it.

In the spreadsheet already open on my desktop, sort the Budget tab by due date. Stop before saving.

A Use your computer card appears with the goal, the model, the data it sends, and the access it takes. Allow grants access for that one response. For now keeps it for the current session until you stop it. Deny leaves the desktop untouched, and you can do the step yourself or ask differently.

While Bearly works, a Computer control sits beside the chat input showing whether it is starting, looking, or working in an app. The response keeps an activity record of the app and the actions involved. Selecting Stop ends the task and revokes the session grant.

The access is broad, and the card says so. Bearly can capture screenshots of your full display and send them to the model handling the task. It can change focus, move between visible windows, and control the mouse and keyboard. The scope named at the start may be one app, but an approved task can move to another visible window. Close or hide anything you would not want included before you approve. Some actions raise a second confirmation before they run.

Computer Use makes mistakes, the way a person moving quickly through an interface does. For consequential work, say where to pause — before sending a message, submitting a form, saving over a file, or confirming a purchase.

Connectors take any MCP server

Until now, Connectors offered a fixed list: Notion, Linear, GitHub, Stripe, Figma, and ten more. The list was the boundary. If the system you cared about was not on it, there was nothing to do.

App Settings → Connectors → Add custom MCP server now takes either the HTTPS address of a Streamable HTTP MCP server, or, in the desktop app, an npm package.

An HTTPS server works in a desktop browser and in the desktop app. Authenticate with MCP OAuth, a bearer token, custom headers, or nothing at all. Those values stay in the current Bearly browser or desktop profile, and Bearly attaches them only to requests for the address you entered.

An npm package runs on your own computer. Bearly prepares a runtime it installs and manages, so Node and npm do not need to be there already. Its variables live with the device's other environment variables under App Settings → Runtime, which that device's skills and local commands can also read.

That difference is the one to hold on to. A remote server receives whatever a tool call includes. A local package runs as you and can reach the files your account can reach. Add a server because you know who publishes it, not because the name sounds useful.

Servers you add sit beside the built-in services and behave the same way. Connecting one is not the same as using it: open Connectors in the context strip and turn it on for the conversation where you want it. In a Routine, each connector also carries a Tools setting of All or Read-only, so a scheduled run can read your issue tracker every morning without being able to write to it.

Team admins can supply servers through a policy. Every member on that policy gets the same server definition and enters their own credentials, and the policy decides whether members may add personal servers at all.

Where they run

Computer Use is desktop-only: macOS, Windows, and Linux in the Bearly desktop app. A conversation that used it stays readable everywhere, but return to the desktop app before asking Bearly to look at your computer again. macOS asks for Accessibility and Screen Recording permission the first time. On Windows, Bearly offers a small helper that makes protected and background windows more reliable; it installs for everyone on the PC, so Windows asks for administrator approval.

Connectors work in a desktop browser and the desktop app, and are not available in the iOS and Android apps or in mobile and tablet browsers. HTTPS servers work in both places; npm packages need the desktop app.

Neither feature depends on your plan. Both are available by default, and both can be turned off — for yourself, or across a managed team under Code & Automation in a team policy.