toone

Feature · Connect

MCPs and integrations

Give agents extra tools through MCP servers and reusable browser integrations, scoped to one project or your whole Mac, with no secrets in routines.

Product guide · MCPs and integrations

Extend what agents can do

MCP servers provide structured tools beyond Toone’s native project surface. Enable the servers a workflow needs and provide required credentials without embedding secrets in routine instructions.

API key… asks for the server's credential and keeps it in your macOS Keychain.

MCPs and browser integrations are not available in the Mac App Store edition. Toone's built-in tools still work there.

Choose the scope

Global MCPs are available across projects on the Mac. Project-specific tools belong with the project that needs them, keeping capabilities from appearing everywhere by default.

Settings → MCPs: switch on servers for every project on this Mac.

Reuse browser integrations

Browser site maps describe repeatable interactions with a web service. Toone keeps them in one collection on your Mac, shared by all your projects, so a map that one project builds is ready for the others. Settings → MCPs lists them under Global Integrations, where you can turn a map off.

Settings → MCPs → Global Integrations: every project shares these site maps; switch one off here.

Keep access deliberate

An enabled tool expands what an agent can reach or change. Match each MCP and browser integration to a defined agent responsibility, and disable global capabilities that are no longer needed.

Turn MCP servers on per project from the Organization tree; an orange dot means the server still needs its API key.

Next: AI providers.