Skip to main content
An AI coding agent running on your machine, such as Claude Code or Codex, can work on your QuivaWorks account directly: build and publish flows, define record sets, pull a configuration to a file, change it and push it back, or copy a setup from one account to another. There are three pieces, and you can use any of them:

The credential: a user API key

Everything here authenticates with a user API key. Create one in Settings → API keys → Add (see API keys for MCP). It acts as you: it reaches every endpoint your user can, with your role. A key created in Settings expires after 90 days.
API integrations (Account → Connections, with a client ID and secret) are a different thing. They are the machine identity for task sync and are not used to drive your account from an agent.

Your account id

A profile is tied to one account. You do not need to look the id up: profile add asks the API which account the key belongs to (GET /accounts/info, which returns the account’s id, name and display name) and saves it. --account <account id> is optional. You can also copy it from the app: open Account, and the Account ID row (under Sign-in address) has a copy button.
The Account Branding App name card with a Sign-in address row and an Account ID row with a copy button

The Sign-in address and Account ID rows on Account, Branding. The address has a Set address or Change button; the Account ID has a copy button. Values shown are examples.

If you use an environment variable and want to see the account a key belongs to:
The /u/<code>/ segment in a QuivaWorks address is a session code, not the account id.
The API keys page listing keys with Name, Account, Last 4 Characters, Created and Expires columns and an Add button

Settings, API keys: your keys with the account, last four characters and expiry. Names shown are examples.

Store the key

The local MCP servers look for a key in this order: the profile named by QUIVA_PROFILE, then QUIVA_API_KEY_<PROFILE>, then QUIVA_API_KEY. The remote server takes the key in a request header instead, so set it up with an environment variable.

Remote or local MCP

  • Remote (https://api.quiva.ai/mcp): nothing to install. Your client sends the key on every request. Start here.
  • Local: you run the servers from the repository as processes on your machine. Use them when you develop against the servers or your client cannot make a hosted HTTP connection.

Keep the key safe

Never paste an API key into a chat with an agent: anyone who can read the conversation can act as you. Enter it only at the hidden profile prompt or in an environment variable.
  • Create one key per tool or machine, named for what uses it, so you can revoke one without breaking the rest.
  • Rotate by creating the replacement first, switching your tools to it, then deleting the old key. See API keys.
  • Prefer a restricted key when an agent only needs one area. See API keys for MCP.
  • Do not commit files that contain a key. Use ${QUIVA_API_KEY} references in shared config.