# How to connect Convex to OpenClaw (paste one key, 19 tools) > Connect Convex to OpenClaw with ClawLink: paste your Convex key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/convex The usual route to Convex access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Convex setup: install one ClawHub skill, connect Convex in the browser, and OpenClaw can call real Convex actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Convex. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Convex** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect convex # connect Convex (browser OAuth) npx -y @useclawlink/cli actions convex # list available actions npx -y @useclawlink/cli run convex --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Convex in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Convex API key once. Verify the connection by asking OpenClaw: > Use Convex to execute query batch and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Convex is connected in the dashboard, that agent calls the same 19 Convex tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Convex MCP for OpenClaw Looking for a Convex MCP server for OpenClaw? ClawLink connects Convex to OpenClaw and exposes 19 Convex tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Convex integration](https://claw-link.dev/hermes/convex) works the same way. ## What the OpenClaw Convex integration can do 19 Convex tools are ready for OpenClaw once the account is connected. The 16 below are the ones people reach for most; your agent can call all 19. ### 16 of 19 Convex tools for OpenClaw | Tool | What it does | |---|---| | **Execute query batch** `convex_execute_query_batch` | Execute multiple Convex query functions in a single batch request | | **Get deployment** `convex_get_deployment` | Retrieve details about a Convex cloud deployment | | **Get project by ID** `convex_get_project_by_id` | Retrieve detailed information about a specific Convex project by its ID | | **Get project by slug** `convex_get_project_by_slug` | Retrieve a Convex project by its slug within a team | | **Get query timestamp** `convex_get_query_timestamp` | Get the latest timestamp for queries from Convex deployment | | **Get token details** `convex_get_token_details` | Retrieve token details for the authenticated token | | **List deploy keys** `convex_list_deploy_keys` | List all deploy keys for a specified Convex deployment | | **List deployment classes** `convex_list_deployment_classes` | List available deployment classes for a Convex team | | **List deployment regions** `convex_list_deployment_regions` | List available deployment regions for a Convex team | | **List deployments** `convex_list_deployments` | List all deployments for a Convex project | | **List log streams** `convex_list_log_streams` | List all existing log stream configurations in a deployment | | **List projects** `convex_list_projects` | List all projects for a specific Convex team | | **Create deploy key** `convex_create_deploy_key` | Create a deploy key for use with the Convex CLI | | **Create deployment** `convex_create_deployment` | Create a new deployment for a Convex project | | **Create project** `convex_create_project` | Create a new project on a Convex team, optionally provisioning a dev or prod deployment | | **Update deployment** `convex_update_deployment` | Update properties of an existing Convex deployment | ## Example prompts **Execute Query Batch** > Use Convex to execute query batch and walk me through the result in plain English. **Get Deployment** > Pull the relevant data from Convex, summarize it in plain English, and point out anything that needs attention. **Get Project By Id** > Pull the relevant data from Convex, summarize it in plain English, and point out anything that needs attention. **Get Project By Slug** > Pull the relevant data from Convex, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Convex working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Convex API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Convex account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Convex. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Convex actions to the runtime in a format your agent can reliably use. | 19 tools for Convex are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Convex to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Convex in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Convex key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Convex skill but can't call the tools The ClawHub skill teaches OpenClaw about Convex, but the calls run through the ClawLink plugin and your connected account. Make sure Convex is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Convex from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Convex tools Convex tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Convex call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Convex returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Convex has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Convex integration? Yes. ClawLink is the fastest way to connect OpenClaw to Convex: link your Convex account once in the browser and OpenClaw can call the Convex API through 19 ready-made tools — no custom code or token handling. ### How do I add Convex to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Convex skill from ClawHub, then you click Connect in the dashboard to authorize Convex. OpenClaw calls the tools from the next message — no config files, and the Convex key you paste is stored server-side instead of in your environment. ### How long does it take to connect Convex to OpenClaw? About two minutes. Sign in, click Connect next to Convex in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Convex up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Convex working from chat. ### OpenClaw installed the Convex skill but can't call the tools The ClawHub skill teaches OpenClaw about Convex, but the calls run through the ClawLink plugin and your connected account. Make sure Convex is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.