Can Lyro write to the Convex database?

Not with this toolkit. Execute Query Batch runs several Convex query functions in one request, which reads app data, but nothing here calls a mutation or an action. Writes still go through your own Convex functions.

How much access does a Convex deploy key hand over?

Administrative access to the deployment it was created for. Create deploy key generates credentials for CLI-based development and deployment workflows, and List Deploy Keys shows every key that can deploy to a given deployment - which makes that list worth reviewing periodically, not only appending to.

What does deleting a deployment or a project take with it?

Everything. Delete Deployment removes the deployment along with all of its data and files, and Delete project removes a project and every deployment under it. Neither can be undone, so both belong behind a human decision rather than a chat request.

How does Lyro know which team or project a token covers?

Get token details returns the team ID for a team token or the project ID for a project token, which is the first thing to establish after an OAuth flow. List deployment classes and List deployment regions then show what that team is actually able to provision.

Convex MCP integration

Creates projects and deployments, batches query functions to read app data, issues and audits deploy keys, and reports log streams.

Connect Convex See all integrations

19actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create project
Lyro creates a new Convex project with optional dev or prod deployment. Development teams initialize backend infrastructure in seconds without manual setup.
Get query timestamp
Lyro retrieves the latest query timestamp from a Convex deployment. Engineers verify data freshness and sync timing without checking logs.
Delete project
Lyro permanently deletes a Convex project and all deployments. Teams clean up abandoned projects to reduce costs and administrative clutter.

See all 19 actions

How businesses use Convex + Lyro

Each card is one request a support team gets, and the Convex actions Lyro runs to close it.

Provision a project and its deployment
Lyro checks which regions and deployment classes the team can use, creates the project, and adds the dev, production, or custom deployment it needs.
List Deployment RegionsCreate ProjectCreate Deployment
Read app data without a round trip per question
Lyro runs several Convex query functions in a single batched request, checks the latest query timestamp, and confirms which deployment it is reading from.
Execute Query BatchGet Query TimestampGet Deployment Details
Issue and audit the credentials that can deploy
Lyro establishes which team or project the current token belongs to, generates a deploy key for CLI work, and reports every key that can already deploy there.
Get Token DetailsCreate Deploy KeyList Deploy Keys
Report what a team is actually running
Lyro lists the projects on a team, the deployments under a project, and the destinations each deployment streams logs to, such as Datadog, Axiom, or Sentry.
List ProjectsList DeploymentsList Log Streams

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Convex actions it has and picks the ones a request needs.

01
Connect Convex
Authorize the Convex account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Convex actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Convex · Lyro

Everything else about Convex

Setup, permissions, and the limits of what Lyro can do inside Convex.

Not with this toolkit. Execute Query Batch runs several Convex query functions in one request, which reads app data, but nothing here calls a mutation or an action. Writes still go through your own Convex functions.

Every action available in Convex

All 19 actions your agent can call on Convex, straight from the live MCP connection.

Create deploy key
Create a deploy key for use with the Convex CLI.
Create deployment
Create a new deployment for a Convex project.
Create project
Create a new project on a Convex team, optionally provisioning a dev or prod deployment.
Delete custom domain
Remove a custom domain from a Convex deployment.
Delete deployment
Delete a Convex deployment.
Delete project
Deletes a Convex project and all its deployments permanently.
Execute query batch
Execute multiple Convex query functions in a single batch request.
Get deployment details
Retrieve details about a Convex cloud deployment.
Get project by ID
Retrieve detailed information about a specific Convex project by its ID.
Get project by slug
Retrieve a Convex project by its slug within a team.
Get query timestamp
Get the latest timestamp for queries from Convex deployment.
Get token details
Retrieve token details for the authenticated token.
List deploy keys
List all deploy keys for a specified Convex deployment.
List deployment classes
List available deployment classes for a Convex team.
List deployment regions
List available deployment regions for a Convex team.
List deployments
List all deployments for a Convex project.
List log streams
List all existing log stream configurations in a deployment.
List projects
List all projects for a specific Convex team.
Update deployment
Update properties of an existing Convex deployment.