Use this page for hosted MCP setup, the canonical `SKILL.md`, reusable fixtures, and the public API source contract. Everything below is viewable inline and downloadable.
Start Droviat from the agent surfaces where remote MCP connectors already live, then point them to your hosted workspace integration.
arguments.confirmed=trueStart with the live transport contract, session headers, and a minimal request flow.
| Header | Purpose |
|---|---|
Authorization | Droviat bearer: a user access token, or a workspace API key (usk_…) limited to its granted scopes. |
x-workspace-id | Explicit workspace context for user-token sessions. Optional with API keys, which are workspace-bound. |
x-mcp-client-id | Stable client identifier for connection records. |
x-mcp-client-name | Human-readable client label. |
x-mcp-client-version | Client version metadata for support and audit trails. |
POST /mcp with an initialize request.notifications/initialized after the handshake completes.tools/list to read the current workflow catalog.tools/call with explicit user context for any mutating workflow.arguments.confirmed=true after user approval.POST /mcp
Authorization: Bearer <droviat-access-token>
x-workspace-id: <workspace-id>
x-mcp-client-id: claude-code
{
"jsonrpc": "2.0",
"id": "init-1",
"method": "initialize",
"params": {
"protocolVersion": "2025-11-25",
"capabilities": {},
"clientInfo": {
"name": "claude-code",
"version": "2.1.177"
}
}
}{
"jsonrpc": "2.0",
"id": "call-2",
"method": "tools/call",
"params": {
"name": "campaign_create",
"arguments": {
"name": "Q4 launch",
"slug": "q4-launch",
"status": "draft",
"confirmed": true
}
}
}Register the Droviat remote MCP endpoint as a custom MCP server in Claude Code.
Add the hosted endpoint with the HTTP transport and the required Droviat headers. The
default scope is local (current project, private to you).
claude mcp add --transport http droviat https://api.droviat.com/mcp \
--header "Authorization: Bearer ${DROVIAT_ACCESS_TOKEN}" \
--header "x-workspace-id: ${DROVIAT_WORKSPACE_ID}" \
--header "x-mcp-client-id: claude-code"
Use --scope user to make Droviat available in every project, or
--scope project to share it with your team through a committed
.mcp.json.
Committing this file at the repository root gives every teammate the same connection.
${VAR} references expand from each developer's environment, so tokens stay
out of version control.
{
"mcpServers": {
"droviat": {
"type": "http",
"url": "https://api.droviat.com/mcp",
"headers": {
"Authorization": "Bearer ${DROVIAT_ACCESS_TOKEN}",
"x-workspace-id": "${DROVIAT_WORKSPACE_ID}",
"x-mcp-client-id": "claude-code"
}
}
}
}claude mcp list to confirm droviat shows as connected./mcp to inspect server status and the tool catalog.campaign_list).arguments.confirmed=true after you approve.usk_…) as the bearer: it is workspace-bound, so x-workspace-id becomes optional, and tools are limited to the key's scopes.DROVIAT_ACCESS_TOKEN (and DROVIAT_WORKSPACE_ID for user tokens) in your shell profile instead of inlining values.The canonical skill document for agent-facing Droviat workflow guidance.
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…