MCP and Connectors

The MCP page manages the external and system capabilities Klaus can call.

• Built-in capabilities: Computer Use (lets Klaus click and type to operate desktop apps like a person) appears as a native capability card; click the card to reach its toggle and configuration. (Browser control used to be another native capability card here; it is now a built-in plugin, and its toggle and configuration surface moved to the plugins page.)
• System connectors: connect to macOS local data and apps, such as Messages, Safari bookmarks and history, Photos, App UI, and more. Some connectors require system authorization first (see "System authorization" below) and stay off until you grant it.
• Marketplace and custom: you can install MCP servers from the marketplace, or add custom MCP servers manually. The connector catalog is now fully server-hosted — the client no longer ships a compiled-in seed. The upside is that when the server adds something new, every client sees it without a release; the trade-off is that when the server is unreachable, the connector marketplace is empty (the same trade-off as the skills marketplace).

MCP servers have three scopes: global (available to all sessions), project (written to <project>/.klaus/mcp.json, committed with the repository and shared with the team), and local (written under that project's path in the engine configuration ~/.klaus/config.toml, private to this machine and never committed). The "Installed" section starts with a row of tabs: "Global" plus one tab per registered project; inside a project tab, each row is labelled "project" or "local" to show which kind it is. Project-scoped configuration is read when a session starts, so after changing it you need to open a new session for it to take effect. Also, MCP servers brought in by a plugin carry a "plugin" source tag on their row — that is a source label, not a scope you can choose. When a server is installed but its tools do not show up, the causes in order of likelihood are: servers that need authorization (OAuth) stay unavailable until you complete it — the MCP page marks these servers separately so you can authorize them in place; next is a missing runtime that the launch command depends on (npx/uv and the like — the MCP page has a detection entry point); then the server itself, or that individual tool, being switched off — a single tool can be turned off on its own without disabling the whole server.

(Historically there was also a "project trust" gate; it has been removed: tools are no longer withheld because trust was never confirmed.)