MCP and agents
Set up an MCP client
Connect a local MCP client to Braus to observe and operate macOS applications, use Chrome and, if you allow it, read passive interaction events and shared memory. Your client supplies the model; the running Braus app supplies the tools.
Braus exposes its bridge over local STDIO, so the client and Braus run on the same Mac. The helper is included in Braus.app and needs no separate Node.js or Python installation. There is no public HTTP or SSE endpoint and no hosted OAuth connector. Tool results go to your client and may be sent to its model provider: a local bridge does not mean local model inference.
Prepare Braus
- Put Braus.app in a stable location, such as
/Applications, then open it. Keep Braus running while a client uses its tools. - Grant the macOS permissions Braus requests for the features you use: Accessibility and Screen Recording for desktop control and perception, Input Monitoring for passive watching. Chrome connection authorization is separate.
- Open MCP → MCP Connections… from Braus’ menu bar.
- Name the client, select its capabilities and click Add Client. Create a separate entry for each client you connect.
- Turn Enabled on and wait for Ready.
- Expand Client configuration and use Copy Claude Code command, Copy Codex command or Copy JSON. These carry your actual paths and client ID.
The generated configuration is the preferred way to install. The examples on this page are public templates: they are not credentials, and they do not run until you replace the placeholders.
| Value | Example |
|---|---|
| Bundled helper | /Applications/Braus.app/Contents/Helpers/braus-bridge |
| Client connection file | /Users/YOUR_USERNAME/Library/Application Support/Braus/MCP/CLIENT_UUID.connection.json |
Replace YOUR_USERNAME and CLIENT_UUID with the values copied from Braus. If Braus is elsewhere or uses a custom support directory, use the generated paths instead. Do not create a connection file yourself or copy another person’s file.
Use absolute paths in JSON and TOML; do not substitute ~ or $HOME there. Keep the spaces inside each path string: an argument containing a path is one argument. braus-bridge is the executable; mcp-bridge is its required first argument.
Merge the entry into the client’s existing settings and keep unrelated servers. These machine-specific settings belong in your personal configuration, not in a shared repository.