search_zdravo
Search personal Zdravo memories available to the authenticated integration.
Developer guide / MCP
The Zdravo MCP server exposes context tools to compatible clients such as Claude Desktop and Cursor. Adding an MCP server does not proxy or disable the other tools available to an agent; those actions must be routed through a separately supported governed execution path.
Quick start
Start in the guided setup to select an organization, connect a remote MCP client with OAuth, and run a read-only governed test that returns a decision receipt. Local stdio setup remains available for teams that need it.
Open guided setupClaude Desktop configuration
{
"mcpServers": {
"zdravo": {
"command": "npx",
"args": ["-y", "zdravo-mcp@2.6.0"],
"env": {
"ZDRAVO_API_KEY": "REPLACE_WITH_YOUR_SCOPED_KEY",
"ZDRAVO_API_URL": "https://zdravo.ai"
}
}
}
}This legacy local stdio option stores a scoped API key in the client configuration. Prefer the hosted OAuth setup when supported.
Remote MCP / Streamable HTTP
Add this remote server URL to a compatible client and complete Zdravo’s OAuth consent flow. The hosted gateway uses Streamable HTTP and does not require you to run a separate service. Consent binds organization access to a specific organization, and the guided setup can produce a verified decision receipt.
Remote client settings
In Settings → Integrations → MCP setup, choose the organization, authorize the client, and run the read-only governed test. A completed result includes the decision and invocation IDs so an administrator can inspect the corresponding receipt in Decision Center.
Open guided setupCurrent capabilities
Available tool names and behavior are defined by the installed server release and the credentials it uses. The MCP connection does not automatically mediate tools owned by the AI client.
Search personal Zdravo memories available to the authenticated integration.
Save conversation context or a memory through the Zdravo MCP server.
The server also documents organization-context tools such as search_org_memories and get_team_context; available results depend on account access.
Client setup
Restart the client after saving the configuration and confirm the Zdravo server and its tools appear in the client’s MCP interface. This confirms connectivity—not that other tools or agent actions are governed by Zdravo.
Add the JSON above to Claude Desktop’s MCP server configuration, restart Claude Desktop, then verify the Zdravo tools appear.
Add an equivalent server entry through Cursor’s MCP settings, restart or reload MCP servers, then verify the Zdravo tools appear.