API & MCP Access

Queml is fully programmable. Anything you can do by clicking around the Portal, you can also drive from your own code: manage your voice apps with the API, and connect AI clients to Queml over the Model Context Protocol (MCP) so you can build and edit flows by simply describing what you want. This page covers how to authenticate, how to connect an MCP client, and how flows themselves can reach back out to your systems while a call is in progress.

Authentication

Generate an API token from your account settings. Each token is scoped to your tenant — the isolated space that holds your apps, numbers, recordings, and call data — so it can only ever read or change resources that belong to you. Treat tokens like passwords: keep them secret, store them outside of source control, and rotate or revoke any token you suspect has leaked. You can issue more than one token, which makes it easy to retire a single integration without disrupting the rest.

MCP protocol

Queml speaks the Model Context Protocol, so you can connect from VS Code, Cursor, or any MCP-compatible client and manage your voice apps conversationally. Instead of stepping through the builder by hand, you ask your AI client to make the change — "add an after-hours menu," "transfer billing calls to the queue" — and it talks to Queml on your behalf over MCP. This pairs naturally with the VS Code extension, giving you a single place to write, review, and ship flow changes without leaving your editor.

Calling APIs from a flow

The API works in both directions. Beyond managing apps from the outside, your flows can call out to your systems while a call is live. The Script and Webhook actions query REST APIs and send call events to your backend in real time — look up an order, check availability, or verify an account before the caller hears a response, and feed events into your own systems to build dashboards, trigger workflows, or log every call as it happens. See the Actions Reference for how each action works, and the Integrations section for connecting Queml to the services you already run.

Flows as code with GitHub

Flow configurations don't have to live only in the Portal. With the GitHub integration you can manage them as code — keep every flow under version control, review changes in pull requests, and collaborate with your team the same way you do with the rest of your codebase. That gives you a full history of who changed what, a clean review step before anything goes live, and an easy path to roll back if a change doesn't work out.

Related

• Quick Start — build and launch your first voice app.
• Actions Reference — the Script, Webhook, and every other action.
• VS Code Extension — edit flows from your editor over MCP.
• Integrations — connect Queml to the services you already use.