Description
The SDK Agent Axis packages the contracts an external agent needs to consume Dots safely and understand its structured operating context. createDotsAgentClient enables the agent marker and captures safely parsed DBOM side channels. The subpath exports DBOM readers, vault boundary helpers, instruction hierarchy, tool-event classifiers, and a Node-only MCP server entry point isolated from browser barrels.
The workflow is designed for agent and MCP developers. It uses the same authenticated, company-scoped service contracts as the rest of Dots, so terminal or protocol convenience never creates a second source of truth. Inputs are validated before or at the route boundary, and outputs preserve identifiers and structured details needed for a reliable next step.
Selling Points
- Makes agent mode and operating-manual capture the default rather than an integration afterthought.
- Provides typed tier readers for trusted Dotabase guidance.
- Shares the same injection-resistant vault boundary as the MCP runtime.
- Classifies tool activity into stable events for agent UX and observability.
- Offers both browser-safe agent helpers and an explicitly Node-only MCP entry.
User Story
An agent developer creates the agent-default client, receives a tier-two DBOM during a write, renders retrieved text inside the shared vault boundary, and classifies returned tool events for the host UI. The integration follows Dots' instruction hierarchy by construction. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The axis is pluggable: packages/sdk/src/internal/agent/create-dots-agent-client.ts accepts client configuration and a DBOM sink, while packages/sdk/src/public/mcp/index.ts exposes the MCP composition point. The rating reflects the most-open supported seam that is true for this capability, not a transitive implementation detail. The cited path is the operational proof: consumers can use the documented seam, while unsupported changes still require a core release.
Capabilities & Limits
- Capability: Agent-default client with typed, contained DBOM capture.
- Capability: Boundary helpers, instruction hierarchy, and tool-event classification.
- Capability: Primary MCP server entry plus generated capability discovery.
- Limit: The committed discovery artifacts are generated files; live serving of
llms.txtover a public route remains a named successor.
The limit is intentional product truth rather than missing documentation. Calls also remain subject to authentication, tenant selection, schema validation, and the permissions enforced by the authoritative service.
Implementation Map
packages/sdk/src/internal/agent/create-dots-agent-client.tspackages/sdk/src/internal/agent/dbom.tspackages/sdk/src/public/mcp/index.ts