Convex
for LuumenAI
Read Convex projects and deployments, then make changes as approved steps
Connect Convex and your agent can see the shape of your backend: which projects a team owns, what deployments sit under each one, which deploy keys exist, and how log streams are configured. It reads that on request and answers right away. Changes like creating a deployment or issuing a deploy key are previewed first and go out as approved, audited steps.
The Convex toolbox
19 tools: 12 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadExecute Query BatchExecute multiple Convex query functions in a single batch request.
- ReadGet Deployment DetailsRetrieve details about a Convex cloud deployment.
- ReadGet Project by IDRetrieve detailed information about a specific Convex project by its ID.
- ReadGet Project by SlugRetrieve a Convex project by its slug within a team.
- ReadGet Query TimestampGet the latest timestamp for queries from Convex deployment.
- ReadGet token detailsRetrieve token details for the authenticated token.
- ReadList Deploy KeysList all deploy keys for a specified Convex deployment.
- ReadList deployment classesList available deployment classes for a Convex team.
- ReadList deployment regionsList available deployment regions for a Convex team.
- ReadList DeploymentsList all deployments for a Convex project.
- ReadList Log StreamsList all existing log stream configurations in a deployment.
- ReadList ProjectsList all projects for a specific Convex team.
- WriteCreate deploy keyCreate a deploy key for use with the Convex CLI. Approval by default
- WriteCreate DeploymentCreate a new deployment for a Convex project. Approval by default
- WriteCreate ProjectCreate a new project on a Convex team, optionally provisioning a dev or prod deployment. Approval by default
- WriteDelete Custom DomainRemove a custom domain from a Convex deployment. Approval by default
- WriteDelete DeploymentDelete a Convex deployment. Approval by default
- WriteDelete projectDeletes a Convex project and all its deployments permanently. Approval by default
- WriteUpdate DeploymentUpdate properties of an existing Convex deployment. Approval by default
One prompt, start to finish
What a governed Convex run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create deploy key, create deployment, create project, delete custom domain, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Convex — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Convex to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.