Skip to main content
Most people should use the hosted remote server instead — nothing to clone or run. Run the servers locally when you’re developing against them, or where a hosted HTTP connection isn’t an option for your client. This repository is separate from the main Quiva application.

​
Requirements

  • Node.js 18 or later (the servers use the global fetch)
  • A Quiva API key — see API keys

​
Clone and install

If you can’t access this repository, contact support.
Each server lives in its own package (quiva-flows-mcp, quiva-records-mcp, quiva-documents-mcp, quiva-workspaces-mcp, quiva-agents-mcp, quiva-distribution-mcp, quiva-coworker-mcp) and runs as an independent stdio process — connect to only the ones you need.

​
Configure credentials

Each server reads its own .env file:
Fill in one of the following (checked in this order if more than one is set): QUIVA_API_URL defaults to production (https://api.quiva.ai); leave it unset unless you’re pointed at a different environment.
The Abbie coworker server needs an admin or root user for its account-wide writes (organisation profile, task space, organisation environment). An email/password login or bearer token for such a user works; an API key does too, since the gateway resolves it to the same token.

​
Register with your client

​
Claude Code

Add each server you want:
Repeat for the other packages, changing the directory and env prefix. If the repository ships a .mcp.json at its root, opening a session inside that checkout registers everything in it automatically — approve the servers when Claude Code prompts you, and restart the session after adding credentials (MCP servers connect at session start).

​
Other clients

Any MCP client that launches a local command over stdio can run these the same way: point it at sh <package>/bin/run.sh with the environment variables above set, either in the client’s own config or via each package’s .env file.

​
Tool names

Running locally, each server’s tools are unprefixed — list_workflows, not flows_list_workflows — since only one server’s tools are loaded into that client connection at a time. The tool reference lists both the bare name and the prefix it carries on the hosted remote server.

Tool reference

Every tool, by server, with what it does