Connected tools · MCP

Connect Halo to anything.

Halo speaks the Model Context Protocol, so it can use your database, your CRM, your wiki, your smart home, and thousands of community tools, without a new build.

Point Halo at any MCP server, local or remote, and its tools become things Halo can do, ranked and routed on-device alongside the built-in ones. Capability becomes config, not a recompile.

Local-first Opt-in per server Never auto-fires

How it works

Config, not a recompile.

01

Paste a server, not a plugin

Add a server in Settings under Connected tools by pasting an mcpServers config, the same JSON other MCP apps use. No SDK to learn, no recompile, no waiting on us to ship a build.

02

Halo discovers its tools

On connect, Halo lists the server's tools and resources and registers them live. They're ranked on-device, so your prompt stays lean even when a server exposes dozens of tools.

03

The same gates as everything else

A connected tool is treated exactly like a built-in one: the same confirm card, risk gating, undo, and audit trail. Nothing about being external is special-cased downstream.

Local servers stay local

A local server runs as a process on your Mac. Its data never leaves your machine, so a database or a home bridge you connect is as private as everything else Halo does.

Remote servers are badged, and off by default

A remote server carries a clear "Sends data off your Mac" badge. It's opt-in per server, never auto-fires, and always shows a confirm card before it runs, with the same undo and audit trail as any built-in action.

No plugin SDK of our own. Halo adopts the open standard, so a server you already use elsewhere works here too.

FAQ

Questions, answered.

What is MCP?

The Model Context Protocol is an open, industry-standard way to connect an AI assistant to external tools and data. Halo is an MCP client, so it works with any MCP server, including the thousands the community has already built.

Do I need to write code?

No. Paste a server's config in Settings under Connected tools, the same mcpServers JSON format other MCP apps use, and Halo connects and discovers its tools.

Does connecting a tool send my data off my Mac?

Local servers run as a process on your Mac, so their data never leaves. Remote servers carry a clear "Sends data off your Mac" badge and are off by default. You choose, per server.

Can Halo act on its own through a connected tool?

No. Every external tool is high-risk by design: opt-in per server, never auto-approved, and it always shows a confirm card before it runs. The same undo and audit trail apply.

Give Halo the tools you already use.

Free on your Mac. Connect a server in a minute, and keep every action on a leash.