@zerobuild/mcp-core

Shared MCP tool, resource, and prompt registrations for Zerobuild.

This package is internal to the Zerobuild monorepo — it's used by @zerobuild/mcp (the npm stdio binary) and by the hosted MCP endpoint at https://mcp.zerobuild.ai. Both transports register the same tools, resources, and prompts from this package, so the contract is identical across stdio and HTTP.

If you're an end user looking to connect an MCP client to your Zerobuild workspace, you almost certainly want one of:

• The hosted endpoint: https://mcp.zerobuild.ai — see the docs.
• The stdio package: @zerobuild/mcp — for self-hosters and on-prem.

This package is published mainly so the stdio binary can install cleanly from npm; direct consumers are rare.

What it exposes

• ZerobuildClient — HTTP client for the Zerobuild REST API. Forwards X-API-Version on every request.
• wrapTool(server, name, description, schema, scopes, handler) — registers an MCP tool with a scope check that returns isError: true on denial (recoverable for the agent).
• TOOL_SCOPES / hasScope(granted, required) — single source of truth for tool → scope mapping.
• VERSIONS, LATEST, getVersion(date?) — version registry.
• register*Tools / register*Resources / registerPrompts — registration functions for each MCP surface, parameterized by ToolContext = { client, scopes }.

Versioning

Date-based, matching the underlying Zerobuild REST API. Today there's a single contract version, 2026-04-09. Adding a future version is a one-file change in src/versions/{date}/index.ts plus a registry entry — see the inline comment in src/versions/meta.ts.

License

MIT.