# How to connect BSC Designer to OpenClaw (paste one key, 10 tools) > Connect BSC Designer to OpenClaw with ClawLink: paste your BSC Designer key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bsc-designer The usual route to BSC Designer 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 BSC Designer setup: install one ClawHub skill, connect BSC Designer in the browser, and OpenClaw can call real BSC Designer 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 BSC Designer. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect BSC Designer** — 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 bsc-designer # connect BSC Designer (browser OAuth) npx -y @useclawlink/cli actions bsc-designer # list available actions npx -y @useclawlink/cli run bsc-designer --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 BSC Designer in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your BSC Designer API key once. Verify the connection by asking OpenClaw: > Use BSC Designer to download excel report 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 BSC Designer is connected in the dashboard, that agent calls the same 10 BSC Designer 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). ## BSC Designer MCP for OpenClaw Looking for a BSC Designer MCP server for OpenClaw? ClawLink connects BSC Designer to OpenClaw and exposes 10 BSC Designer 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 BSC Designer integration](https://claw-link.dev/hermes/bsc-designer) works the same way. ## What the OpenClaw BSC Designer integration can do 10 BSC Designer tools are ready for OpenClaw once the account is connected. ### All 10 BSC Designer tools for OpenClaw | Tool | What it does | |---|---| | **Download excel report** `bsc_designer_download_excel_report` | Generate and download a scorecard's Excel report, optionally evaluated at a specified date | | **Get document** `bsc_designer_get_document` | Get metadata and sharing settings for one scorecard document by numeric ID or alias | | **Get grouped indicator values** `bsc_designer_get_grouped_indicator_values` | Get one indicator's values grouped by day, week, month, quarter, half-year, or year over an | | **Get indicator value** `bsc_designer_get_indicator_value` | Get one indicator's value, baseline, target, minimum, and maximum for the requested as-of date | | **Get scorecard item** `bsc_designer_get_scorecard_item` | Get detailed metadata for one scorecard item, such as an indicator, goal, or initiative, using | | **List documents** `bsc_designer_list_documents` | List scorecard documents owned by or shared with the connected user, returning IDs and aliases | | **List scorecard items** `bsc_designer_list_scorecard_items` | List the goals, perspectives, indicators, initiatives, risks, rationales, and expected outcomes | | **Set indicator values** `bsc_designer_set_indicator_values` | Set one or more indicators' value, baseline, target, minimum, or maximum in one batch request | | **Update indicator** `bsc_designer_update_indicator` | Update an indicator's name, description, or leading/lagging business type without changing its | | **Balance scorecard weights** `bsc_designer_balance_scorecard_weights` | Recalculate and persist balanced indicator weights across a scorecard, returning every changed | ## Example prompts **Download Excel Report** > Use BSC Designer to download excel report and walk me through the result in plain English. **Get Document** > Pull the relevant data from BSC Designer, summarize it in plain English, and point out anything that needs attention. **Get Grouped Indicator Values** > Pull the relevant data from BSC Designer, summarize it in plain English, and point out anything that needs attention. **Get Indicator Value** > Pull the relevant data from BSC Designer, 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 BSC Designer working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the BSC Designer API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BSC Designer 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 BSC Designer. | 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 BSC Designer actions to the runtime in a format your agent can reliably use. | 10 tools for BSC Designer are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes BSC Designer 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 BSC Designer in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the BSC Designer 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 BSC Designer skill but can't call the tools The ClawHub skill teaches OpenClaw about BSC Designer, but the calls run through the ClawLink plugin and your connected account. Make sure BSC Designer 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 BSC Designer 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 BSC Designer tools BSC Designer 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 BSC Designer 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. ### BSC Designer 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 BSC Designer has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw BSC Designer integration? Yes. ClawLink is the fastest way to connect OpenClaw to BSC Designer: link your BSC Designer account once in the browser and OpenClaw can call the BSC Designer API through 10 ready-made tools — no custom code or token handling. ### How do I add BSC Designer to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BSC Designer skill from ClawHub, then you click Connect in the dashboard to authorize BSC Designer. OpenClaw calls the tools from the next message — no config files, and the BSC Designer key you paste is stored server-side instead of in your environment. ### How long does it take to connect BSC Designer to OpenClaw? About two minutes. Sign in, click Connect next to BSC Designer in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring BSC Designer 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 BSC Designer working from chat. ### OpenClaw installed the BSC Designer skill but can't call the tools The ClawHub skill teaches OpenClaw about BSC Designer, but the calls run through the ClawLink plugin and your connected account. Make sure BSC Designer 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 PostHog integration](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.