Quario Developer Portal

Call Quario tool capabilities over plain HTTPS or streamable HTTP MCP. Automatically projected from the canonical catalog with identical authority, validation, rate limits, and asynchronous HITL approvals.

Protocol Baseline

Built on MCP Protocol version 2025-06-18 over streamable HTTP transport, supporting both interactive AI clients and standard HTTP callers.

Authentication

Provide a Personal Access Token (PAT) starting with qmcp_ or an OAuth 2.1 Bearer token (with PKCE) minted for resource https://dev.quario.dev/api/v1.

Authorization: Bearer qmcp_...

Granular Scopes

Access is strictly scoped per operation (e.g. calendar:read, crm:leads:write, email:send). Unscoped tools return 403 Forbidden.

HITL Approvals (REST 202 vs MCP)

Sensitive operations require human operator confirmation:

• REST Door: Returns HTTP 202 Accepted with { approvalId }. Poll status via:GET /api/v1/approvals/{id}
• MCP Protocol: Returns a structured tool result with isError: true containing the approval request and review link, pausing side effects until human approval.

cURL Example

curl -X POST \
  https://dev.quario.dev/api/v1/tools/search_crm_contacts \
  -H "Authorization: Bearer qmcp_..." \
  -H "Content-Type: application/json" \
  -d '{"query":"Acme"}'

SDK Distribution

@quario/sdk is currently a private workspace package for local/monorepo consumption, exporting typed tool schemas and client runners from @quario/sdk. External integrations interact via the REST door or streamable MCP endpoints.