Connect your AI assistant (MCP)
CoverWarden ships a Model Context Protocol (MCP) server, so AI assistants that speak MCP — Claude, and a growing list of agent tools — can work with your vendor book directly: check who's compliant, see what a sub still owes, fetch upload links to send out, or ask free-form questions. Same keys, same permissions, same limits as the REST API.
Connecting
The endpoint is https://app.coverwarden.com/api/mcp (streamable HTTP). Authenticate with an API key from Settings → API as a bearer token — API access is included in the Portfolio and Prequal plans. In Claude Code: claude mcp add coverwarden https://app.coverwarden.com/api/mcp --transport http --header "Authorization: Bearer coi_…". Most MCP clients accept the same URL + Authorization header pair.
What the assistant can do
Six tools, mirroring the dashboard:
- list_vendors — filter by compliance status, incomplete document packets, upcoming expirations, escalation state or name.
- get_vendor — the full picture for one vendor: verdict with issues, latest certificate extraction, document checks, chase history.
- get_upload_link — the vendor's no-login upload URL, ready to paste into an email.
- compliance_summary — org-wide counts at a glance.
- ask_vendor_book — free-form questions ("who expires this month and still owes an EMR letter?").
- create_vendor — add a vendor to track (full-access keys only).
Permissions and limits
Read-only API keys expose only the read tools — an assistant with a read key can never modify anything. All MCP traffic counts against the same per-key burst limit and daily API budget as the REST API, and every write is attributed to the key in the activity log, exactly like REST calls.