Convex MCP integration for AI agents.
Connect AI agents to Convex through 23 structured actions, including execute query batch, create deployment, and create deploy key. Review authentication, in…
- ACTION CONTRACTS
- 23
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Convex integration exposes
The Convex Agent App exposes 23 provider-backed actions for developer tools work. Its current contract lets an authorized agent execute multiple convex queries against a deployment and return results in the same order, create a new deployment in a convex project, and create a deploy key for a convex deployment. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Convex account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Convex capabilities.
Showing 12 of 23 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
execute_query_batchREADExecute multiple Convex queries against a deployment and return results in the same order.
INPUTS: queries / deployment_url
create_deploymentWRITECreate a new deployment in a Convex project.
INPUTS: project_id / type / class / region / reference
create_deploy_keyHIGH IMPACTCreate a deploy key for a Convex deployment.
INPUTS: deployment_name / name
create_projectWRITECreate a Convex project on a team, optionally provisioning an initial dev or prod deployment.
INPUTS: team_id / projectName / deploymentType / deploymentClass / deploymentRegion
delete_custom_domainHIGH IMPACTRemove a custom domain from a Convex deployment.
INPUTS: deployment_name / domain
delete_deploy_keyHIGH IMPACTDelete a deploy key for a Convex deployment.
INPUTS: deployment_name / id
delete_deploymentHIGH IMPACTDelete a Convex deployment and all of its data.
INPUTS: deployment_name
delete_projectHIGH IMPACTDelete a Convex project and all of its deployments.
INPUTS: project_id
get_deploymentREADGet a cloud deployment by deployment name.
INPUTS: deployment_name
get_project_by_idREADGet a Convex project by numeric project ID.
INPUTS: project_id
get_project_by_slugREADGet a Convex project by team identifier or slug plus project slug.
INPUTS: team_id_or_slug / project_slug
get_token_detailsREADReturn the current Convex token details so you can discover the authorized team or project context.
INPUT CONTRACTS
Know what the action needs before it runs.
execute_query_batch
queriesREQUIRED- Convex query calls.
deployment_urlOPTIONAL- The hosted *.convex.cloud deployment URL or deployment name prefix.
create_deployment
project_idREQUIRED- The Convex project ID.
typeREQUIRED- Deployment type.
classOPTIONAL- The deployment class.
regionOPTIONAL- The deployment region.
referenceOPTIONAL- The deployment reference.
create_deploy_key
deployment_nameREQUIRED- The deployment name.
nameREQUIRED- The deploy key name.
create_project
team_idREQUIRED- The Convex team ID.
projectNameREQUIRED- The project name.
deploymentTypeOPTIONAL- The initial deployment type.
deploymentClassOPTIONAL- The deployment class.
deploymentRegionOPTIONAL- The deployment region.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Execute Query Batch
Execute multiple Convex queries against a deployment and return results in the same order. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
execute_query_batchControl Create Deployment
Create a new deployment in a Convex project. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_deploymentVerify with Create Deployment
Create a new deployment in a Convex project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_deploymentSAFETY BOUNDARY
Operate Convex with explicit limits
- Authorize Convex with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `create_deploy_key`, `delete_custom_domain`, and `delete_deploy_key` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `convex.deploy_keys.write`, `convex.deployments.write`, `convex.projects.write`, and `convex.custom_domains.write`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Convex task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
Convex deploy key used with the Authorization Bearer header. Create it from Deployment Settings in the Convex dashboard as documented at https://docs.convex.dev/production/access-tokens.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 11
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 6
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Convex.