Built-in MCP Server

One Mind Across Every Machine · Shipped · workstation, home

Halbert exposes its own tools and resources for external agents to consume via the Model Context Protocol.

Halbert doesn’t just consume MCP tools — it exposes its own capabilities as an MCP server. External agents (Claude, other Halbert instances, custom tooling) can discover and invoke Halbert’s tools, access its discovered resources, and query its knowledge base through the standard MCP JSON-RPC interface.

The MCP server module implements the tools/list and tools/call endpoints, exposing Halbert’s tool registry to external consumers. A camera gate module controls which vision-related resources are exposed based on privacy configuration.

Limits and invariants

The MCP server respects the same policy engine as internal tool calls — external agents cannot bypass permission boundaries.

Where this lives

• halbert_core/halbert_core/mcp/server.py
• halbert_core/halbert_core/mcp/camera_gate.py