Access & credentials

Manage provider keys, API keys, and MCP access for your account.

Provider keys

Workflows run on your own provider account, so add a key for any provider your workflows use — nothing runs on the platform's keys. Keys are encrypted at rest (AES-256-GCM) and only ever used server-side to run your own workflows. The one exception is the description writer in the publish dialog, which is free and runs on the platform's own key.

Loading providers…

API keys

Keys authenticate MCP clients and API calls (Bearer). Only a SHA-256 hash is stored — the raw key is shown exactly once at creation.

Loading…

Connect the MCP

Point any MCP-capable client at Zyvro using the key above, or the REST API directly.

Connect the MCP

Streamable HTTP JSON-RPC at https://server.zyv.ro/mcp. Pick your client and paste — create a key above and the snippets will carry it.

terminal — one line

claude mcp add --transport http zyvro https://server.zyv.ro/mcp \
  --header "Authorization: Bearer <your-key>"

REST API — same key, same engine

curl -X POST https://server.zyv.ro/api/executions \
  -H "Authorization: Bearer <your-key>" \
  -H "Content-Type: application/json" \
  -d '{"workflow_id":"<workflow-id>","inputs":{}}'