Skip to content
Quevell
Menu

Programmatic access
with defined permissions

Quevell supports MCP and an API. An agent connects as a company service account using the permissions assigned to it.

Request path

  1. Service account
  2. Token or OAuth
  3. Action permission
  4. Project and issue access

A service account for the connection

A service account is a principal for software. A Company administrator issues its token and permissions. It cannot become a Company administrator and has no human session. A token is shown when issued and can be revoked separately.

Read the documentation
Service account list containing a reporting account
A service account for software accessOpen the full frame ↗

MCP for issue work

MCP exposes QQL search, issue reading and creation, comments, time records, transitions, pages and boards. Calls use the product services, so changes appear in Issue history and the company audit trail.

Read the documentation

A token or OAuth

A service-account OAuth client obtains an access token with client_credentials. That token lasts one hour. Use the API to connect issue work to your own processes; its method reference is public.

Read the documentation

Try it with your own work

30 calendar days, up to 10 seats, the full product.