LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

Kvery Scoped Queries

Runs saved queries with your account's own permissions — and scoped tokens can limit a connection to tagged queries only.

by kvery-io ↗Relational SQL Databases✓ Official

LABSCO SUMMARY

Scoping a token to tagged queries is a neater permission model than most database tools manage.

The usual choice is all-or-nothing: either the agent can run queries or it cannot. Tagging queries and issuing a token that only reaches one tag means a reporting assistant and an operational one can share a platform without sharing a blast radius — and the boundary is visible in the tags, which someone can audit. Free tier with no card makes it easy to check whether the model fits.

What it is

Kvery's endpoint over their query platform. The interesting property is the token model: a scoped token restricts what the connection can run.

What you get

Six tools, all run under your account's existing group permissions: kvery_list_queries and kvery_search find saved queries, kvery_get_query returns a query's metadata, parameters and SQL, kvery_execute_query runs one with parameters and returns live results, and kvery_list_groups and kvery_get_context report the groups, user and permissions in play.

Requirements

An API key. There is a free-forever plan with no card. Data is encrypted with AES-256, and scoped tokens limit a connection to queries carrying particular tags.

Setup effort

Paste a URL with a key — add the endpoint to your client