# How to connect Cursor to OpenClaw (paste one key, 5 tools) > Connect Cursor to OpenClaw with ClawLink: paste your Cursor key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/cursor The usual route to Cursor 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 Cursor setup: install one ClawHub skill, connect Cursor in the browser, and OpenClaw can call real Cursor 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 Cursor. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Cursor** — 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 cursor # connect Cursor (browser OAuth) npx -y @useclawlink/cli actions cursor # list available actions npx -y @useclawlink/cli run cursor --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 Cursor in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cursor API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Cursor, summarize it in plain English, and point out anything that needs attention. ### 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 Cursor is connected in the dashboard, that agent calls the same 5 Cursor 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). ## Cursor MCP for OpenClaw Looking for a Cursor MCP server for OpenClaw? ClawLink connects Cursor to OpenClaw and exposes 5 Cursor 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 Cursor integration](https://claw-link.dev/hermes/cursor) works the same way. ## What the OpenClaw Cursor integration can do 5 Cursor tools are ready for OpenClaw once the account is connected. ### All 5 Cursor tools for OpenClaw | Tool | What it does | |---|---| | **Get agent conversation** `cursor_get_agent_conversation` | Retrieve the conversation history for a specific cloud agent | | **Get me** `cursor_get_me` | Retrieve API key information including the key name, creation date, and owner email | | **List agents** `cursor_list_agents` | Retrieve a paginated list of all Cursor Cloud agents | | **List models** `cursor_list_models` | Retrieve the list of available AI models in Cursor | | **List repositories** `cursor_list_repositories` | List GitHub repositories accessible to the authenticated user | ## Example prompts **Get Agent Conversation** > Pull the relevant data from Cursor, summarize it in plain English, and point out anything that needs attention. **Get Me** > Pull the relevant data from Cursor, summarize it in plain English, and point out anything that needs attention. **List Agents** > List the relevant items in Cursor, group them by priority, and recommend what OpenClaw should do next. **List Models** > List the relevant items in Cursor, group them by priority, and recommend what OpenClaw should do next. ## 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 Cursor working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Cursor API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cursor 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 Cursor. | 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 Cursor actions to the runtime in a format your agent can reliably use. | 5 tools for Cursor are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Cursor 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 Cursor in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Cursor 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 Cursor skill but can't call the tools The ClawHub skill teaches OpenClaw about Cursor, but the calls run through the ClawLink plugin and your connected account. Make sure Cursor 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 Cursor 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 Cursor tools Cursor 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 Cursor 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. ### Cursor 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 Cursor has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Cursor integration? Yes. ClawLink is the fastest way to connect OpenClaw to Cursor: link your Cursor account once in the browser and OpenClaw can call the Cursor API through 5 ready-made tools — no custom code or token handling. ### How do I add Cursor to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Cursor skill from ClawHub, then you click Connect in the dashboard to authorize Cursor. OpenClaw calls the tools from the next message — no config files, and the Cursor key you paste is stored server-side instead of in your environment. ### How long does it take to connect Cursor to OpenClaw? About two minutes. Sign in, click Connect next to Cursor in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Cursor 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 Cursor working from chat. ### OpenClaw installed the Cursor skill but can't call the tools The ClawHub skill teaches OpenClaw about Cursor, but the calls run through the ClawLink plugin and your connected account. Make sure Cursor 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 - [DataRobot tools](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [OpenClaw Chatbotkit integration](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.