MCP Server
The published server exposes context and workspace tools to supported MCP clients. It does not intercept their native actions.
Setup and detailsIntegrations
Connect through the entry point that fits your workflow. Context integrations are distinct from action enforcement: MCP and browser capture do not automatically mediate an agent's native tools.
The published server exposes context and workspace tools to supported MCP clients. It does not intercept their native actions.
Setup and detailsA developer-mode MV3 ZIP is available for user-initiated conversation capture on the supported sites listed in the extension guide. It does not intercept AI actions.
Setup and detailsInstall the published zdravo-cli package for terminal workflows. CLI calls do not intercept actions performed by another agent.
Setup and detailsInstall the published zdravo-sdk package for typed application access to Zdravo APIs. The SDK is not an agent execution proxy.
Setup and detailsApplications can integrate through Zdravo's current HTTP and OpenAPI surface. An API client does not automatically mediate external agent tools.
Setup and detailsStart here
Create a scoped key for the integration, then use its setup guide. The published CLI and SDK are API clients; they do not force external agents to route every action through Zdravo.
Set up an MCP client →