# How to connect Datascope to OpenClaw (paste one key, 19 tools) > Connect Datascope to OpenClaw with ClawLink: paste your Datascope 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/datascope The usual route to Datascope 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 Datascope setup: install one ClawHub skill, connect Datascope in the browser, and OpenClaw can call real Datascope 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 Datascope. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Datascope** — 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 datascope # connect Datascope (browser OAuth) npx -y @useclawlink/cli actions datascope # list available actions npx -y @useclawlink/cli run datascope --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 Datascope in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Datascope API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Datascope, 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 Datascope is connected in the dashboard, that agent calls the same 19 Datascope 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). ## Datascope MCP for OpenClaw Looking for a Datascope MCP server for OpenClaw? ClawLink connects Datascope to OpenClaw and exposes 19 Datascope 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 Datascope integration](https://claw-link.dev/hermes/datascope) works the same way. ## What the OpenClaw Datascope integration can do 19 Datascope tools are ready for OpenClaw once the account is connected. ### All 19 Datascope tools for OpenClaw | Tool | What it does | |---|---| | **Get all list elements** `datascope_get_all_list_elements` | Retrieve all items from a specific metadata list in Datascope | | **Get all locations** `datascope_get_all_locations` | Retrieve all locations configured in the DataScope system | | **Get answers v4** `datascope_get_answers_v4` | Retrieve form answers using the v4 API endpoint | | **Get answers with full metadata** `datascope_get_answers_with_full_metadata` | Retrieve last form answers with full metadata from DataScope (limit 600 results) | | **Get form schema** `datascope_get_form_schema` | Retrieve the schema definition for a specific form by its form ID | | **Get forms list** `datascope_get_forms_list` | Retrieve all available forms/tasks from the DataScope system | | **Get last tickets** `datascope_get_last_tickets` | Retrieve the last 5 tickets (findings) from the DataScope system | | **Get list element** `datascope_get_list_element` | Retrieve a specific element from a metadata list by type and ID | | **Get ticket types** `datascope_get_ticket_types` | Retrieve available ticket types (findings types) from the DataScope system | | **List last generated files** `datascope_list_last_generated_files` | Retrieve all generated files (PDFs, Excel) from a specific date range | | **List notifications** `datascope_list_notifications` | Retrieve all notifications (PDF and Excel files) from a date range | | **Change form answer** `datascope_change_form_answer` | Change a specific answer in a submitted form | | **Create list** `datascope_create_list` | Create a new empty list (metadata type) in DataScope with specified list_type | | **Create list element** `datascope_create_list_element` | Create a new list element in a specific metadata list identified by metadata_type | | **Create location** `datascope_create_location` | Create a new location in DataScope with geographic coordinates | | **Create task assign** `datascope_create_task_assign` | Create a task assignment for a specific form, user, and location with a deadline | | **Update list element** `datascope_update_list_element` | Update an existing list element by ID with new name, description, code, or attributes | | **Update location** `datascope_update_location` | Update an existing location in DataScope by ID | | **Update bulk list elements** `datascope_update_bulk_list_elements` | Bulk update metadata list objects with soft deletion of objects not in the incoming list | ## Example prompts **Get All List Elements** > Pull the relevant data from Datascope, summarize it in plain English, and point out anything that needs attention. **Get All Locations** > Pull the relevant data from Datascope, summarize it in plain English, and point out anything that needs attention. **Get Answers V4** > Pull the relevant data from Datascope, summarize it in plain English, and point out anything that needs attention. **Get Answers With Full Metadata** > Pull the relevant data from Datascope, 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 Datascope working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Datascope API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Datascope 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 Datascope. | 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 Datascope actions to the runtime in a format your agent can reliably use. | 19 tools for Datascope are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Datascope 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 Datascope in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Datascope 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 Datascope skill but can't call the tools The ClawHub skill teaches OpenClaw about Datascope, but the calls run through the ClawLink plugin and your connected account. Make sure Datascope 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 Datascope 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 Datascope tools Datascope 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 Datascope 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. ### Datascope 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 Datascope has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Datascope integration? Yes. ClawLink is the fastest way to connect OpenClaw to Datascope: link your Datascope account once in the browser and OpenClaw can call the Datascope API through 19 ready-made tools — no custom code or token handling. ### How do I add Datascope to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Datascope skill from ClawHub, then you click Connect in the dashboard to authorize Datascope. OpenClaw calls the tools from the next message — no config files, and the Datascope key you paste is stored server-side instead of in your environment. ### How long does it take to connect Datascope to OpenClaw? About two minutes. Sign in, click Connect next to Datascope in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Datascope 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 Datascope working from chat. ### OpenClaw installed the Datascope skill but can't call the tools The ClawHub skill teaches OpenClaw about Datascope, but the calls run through the ClawLink plugin and your connected account. Make sure Datascope 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 - [Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [OpenClaw Moco integration](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [Connect ClickUp](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints