Most people should connect Claude by signing in with their Droviat account: see Connect Droviat to Claude. This page covers the secondary API-key path for scripts, self-hosted agents and clients that only send fixed headers, plus the protocol details integrators ask about.
confirmed argument is accepted and ignored. Each tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint so clients can ask before changes.tools/call that passes the scope and workspace checks counts as one API call against the workspace plan quota shared with the public API.isError: true and HTTP 200 (types plan_limit_exceeded, workspace_paused, insufficient_scope), not HTTP errors.A workspace API key is bound to one workspace and limited to the scopes it was created with.
| Header | Purpose |
|---|---|
Authorization: Bearer usk_… | Preferred way to send a workspace API key. |
x-api-key: usk_… | Accepted only when no Authorization header is sent, and only for usk_ keys. Sending both headers returns 400 AMBIGUOUS_AUTH. |
x-mcp-client-id, x-mcp-client-name, x-mcp-client-version | Optional labels for the connection records of API-key callers. |
Credentials in query strings are ignored. An invalid, expired or revoked key gets 401 with WWW-Authenticate: Bearer … error="invalid_token".
tools/list shows only the tools the key's scopes allow. Read tools need links:read or analytics:read; write tools need links:write. Create keys in Droviat under Workspace, Integrations.
Stateless Streamable HTTP with JSON responses.
POST /mcp only. GET and DELETE return 405 with Allow: POST; there is no SSE stream and no session ID.MCP-Protocol-Version values: 2025-11-25, 2025-06-18, 2025-03-26. A request without the header is treated as 2025-03-26; an unsupported value returns 400. initialize answers with your version if supported, otherwise the latest.400 with error -32600.202 with no body.-32601 and unknown tools -32602, both with HTTP 200. Malformed JSON returns 400 with -32700.Origin header from an origin Droviat does not recognize get 403.POST /mcp with an initialize request.notifications/initialized after the handshake completes.tools/list to read the tools your credential allows.tools/call; write tools run on the first call.POST /mcp
Authorization: Bearer usk_<workspace-api-key>
MCP-Protocol-Version: 2025-11-25
{
"jsonrpc": "2.0",
"id": "init-1",
"method": "initialize",
"params": {
"protocolVersion": "2025-11-25",
"capabilities": {},
"clientInfo": {
"name": "my-agent",
"version": "1.0.0"
}
}
}{
"jsonrpc": "2.0",
"id": "call-2",
"method": "tools/call",
"params": {
"name": "campaign_create",
"arguments": {
"name": "Q4 launch",
"slug": "q4-launch",
"status": "draft"
}
}
}Sign in with Droviat (recommended), or use an API key when a fixed header is required.
claude mcp add --transport http droviat https://api.droviat.com/mcpThen run /mcp in Claude Code, sign in to Droviat and choose a workspace.
claude mcp add --transport http droviat https://api.droviat.com/mcp \
--header "Authorization: Bearer ${DROVIAT_API_KEY}"
Use --scope user to make Droviat available in every project, or
--scope project to share it through a committed .mcp.json.
{
"mcpServers": {
"droviat": {
"type": "http",
"url": "https://api.droviat.com/mcp",
"headers": {
"Authorization": "Bearer ${DROVIAT_API_KEY}"
}
}
}
}${VAR} references expand from each developer's environment, so keys stay out of version control.
DROVIAT_API_KEY in your shell profile instead of inlining it.Using a Droviat app session token on /mcp still works for now, but it is deprecated.
Deprecation header and, once the date is set, a Sunset header with the date after which session tokens stop working on /mcp.Sunset header.The canonical skill document for agent-facing Droviat workflow guidance.
This v1 skill and the MCP fixtures below show the earlier header and session-token setup and a
confirmation step. That step is no longer required: write tools run on the first call and a
confirmed argument is ignored. Updated versions will be published here.
Loading source…Synthetic payloads for local testing, demos, prompt scaffolding, and regression setup.
Loading source…Loading source…Loading source…Loading source…Loading source…Loading source…Loading source…Loading source…Loading source…Loading source…Loading source…Loading source…The same OpenAPI source used by the live reference page, viewable inline and downloadable.
Loading source…