# How to connect CrowTerminal to OpenClaw (paste one key, 27 tools) > Connect CrowTerminal to OpenClaw with ClawLink: paste your CrowTerminal key once and 27 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/crowterminal The usual route to CrowTerminal 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 CrowTerminal setup: install one ClawHub skill, connect CrowTerminal in the browser, and OpenClaw can call real CrowTerminal 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 CrowTerminal. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect CrowTerminal** — 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 crowterminal # connect CrowTerminal (browser OAuth) npx -y @useclawlink/cli actions crowterminal # list available actions npx -y @useclawlink/cli run crowterminal --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 CrowTerminal in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your CrowTerminal API key once. Verify the connection by asking OpenClaw: > Use CrowTerminal to analyze engagement 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 CrowTerminal is connected in the dashboard, that agent calls the same 27 CrowTerminal 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). ## CrowTerminal MCP for OpenClaw Looking for a CrowTerminal MCP server for OpenClaw? ClawLink connects CrowTerminal to OpenClaw and exposes 27 CrowTerminal 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 CrowTerminal integration](https://claw-link.dev/hermes/crowterminal) works the same way. ## What the OpenClaw CrowTerminal integration can do 27 CrowTerminal tools are ready for OpenClaw once the account is connected. The 26 below are the ones people reach for most; your agent can call all 27. ### 26 of 27 CrowTerminal tools for OpenClaw | Tool | What it does | |---|---| | **Analyze engagement** `crowterminal_analyze_engagement` | Analyze engagement correlation for every field in your agent's markdown | | **Compare md** `crowterminal_compare_md` | Compare your agent's markdown directly with all stored versions | | **Get byok platform intel** `crowterminal_get_byok_platform_intel` | Get algorithm insights for TikTok, Instagram, and YouTube without client-specific context | | **Get client memory changelog** `crowterminal_get_client_memory_changelog` | Retrieve human-readable change history for a client's memory | | **Get client memory pattern** `crowterminal_get_client_memory_pattern` | Track a specific field over time for trend analysis | | **Get components status** `crowterminal_get_components_status` | Get detailed status of each CrowTerminal service component | | **Get data types** `crowterminal_get_data_types` | Retrieve valid data types for ingestion across platforms | | **Get incidents** `crowterminal_get_incidents` | Retrieve list of recent incidents from CrowTerminal with duration and affected components | | **Get platform intel** `crowterminal_get_platform_intel` | Retrieve algorithm insights for TikTok, Instagram, and YouTube | | **Get sandbox client** `crowterminal_get_sandbox_client` | Get mock client data for testing in the sandbox environment | | **Get sandbox memory** `crowterminal_get_sandbox_memory` | Retrieve mock memory/skill data for testing purposes | | **Get status** `crowterminal_get_status` | Retrieve CrowTerminal service status including overall health, component metrics, and uptime | | **Get status history** `crowterminal_get_status_history` | Get 7-day uptime data points ready for visualization and charting | | **Get uptime** `crowterminal_get_uptime` | Retrieve historical uptime data for CrowTerminal agents | | **List webhooks** `crowterminal_list_webhooks` | List all registered webhooks for the authenticated agent | | **Ping crowterminal** `crowterminal_ping_crowterminal` | Check CrowTerminal service availability via a simple ping endpoint | | **Read bulk memory** `crowterminal_read_bulk_memory` | Read memory for multiple clients at once (up to 50) | | **Run sandbox engagement analysis** `crowterminal_run_sandbox_engagement_analysis` | Run mock engagement analysis in the CrowTerminal sandbox environment | | **Test webhook** `crowterminal_test_webhook` | Test a webhook URL by sending a test payload | | **Validate proposed changes** `crowterminal_validate_proposed_changes` | Validate proposed changes against historical data before updating memory | | **Validate sandbox** `crowterminal_validate_sandbox` | Mock validation endpoint for testing in sandbox | | **Create webhook** `crowterminal_create_webhook` | Register a new webhook for receiving real-time event notifications from CrowTerminal | | **Ingest bulk data** `crowterminal_ingest_bulk_data` | Bulk ingest up to 50 analytics data points at once to CrowTerminal | | **Ingest data** `crowterminal_ingest_data` | Ingest platform analytics data from TikTok Studio, Instagram Insights, or YouTube Analytics | | **Register agent** `crowterminal_register_agent` | Self-register a new agent and obtain an API key | | **Update webhook** `crowterminal_update_webhook` | Update an existing webhook configuration in CrowTerminal | ## Example prompts **Analyze Engagement** > Use CrowTerminal to analyze engagement and walk me through the result in plain English. **Compare Md** > Use CrowTerminal to compare md and walk me through the result in plain English. **Get Byok Platform Intel** > Pull the relevant data from CrowTerminal, summarize it in plain English, and point out anything that needs attention. **Get Client Memory Changelog** > Pull the relevant data from CrowTerminal, 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 CrowTerminal working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the CrowTerminal API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CrowTerminal 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 CrowTerminal. | 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 CrowTerminal actions to the runtime in a format your agent can reliably use. | 27 tools for CrowTerminal are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes CrowTerminal 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 CrowTerminal in the browser, and the 27 tools above work from chat. There is no SDK and no config file, and the CrowTerminal 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 CrowTerminal skill but can't call the tools The ClawHub skill teaches OpenClaw about CrowTerminal, but the calls run through the ClawLink plugin and your connected account. Make sure CrowTerminal 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 CrowTerminal 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 CrowTerminal tools CrowTerminal 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 CrowTerminal 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. ### CrowTerminal 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 CrowTerminal has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw CrowTerminal integration? Yes. ClawLink is the fastest way to connect OpenClaw to CrowTerminal: link your CrowTerminal account once in the browser and OpenClaw can call the CrowTerminal API through 27 ready-made tools — no custom code or token handling. ### How do I add CrowTerminal to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink CrowTerminal skill from ClawHub, then you click Connect in the dashboard to authorize CrowTerminal. OpenClaw calls the tools from the next message — no config files, and the CrowTerminal key you paste is stored server-side instead of in your environment. ### How long does it take to connect CrowTerminal to OpenClaw? About two minutes. Sign in, click Connect next to CrowTerminal in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring CrowTerminal 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 CrowTerminal working from chat. ### OpenClaw installed the CrowTerminal skill but can't call the tools The ClawHub skill teaches OpenClaw about CrowTerminal, but the calls run through the ClawLink plugin and your connected account. Make sure CrowTerminal 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 - [GitHub tools](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.