# How to connect Lumify to OpenClaw (paste one key, 10 tools) > Connect Lumify to OpenClaw with ClawLink: paste your Lumify 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/lumify The usual route to Lumify 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 Lumify setup: install one ClawHub skill, connect Lumify in the browser, and OpenClaw can call real Lumify 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 Lumify. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Lumify** — 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 lumify # connect Lumify (browser OAuth) npx -y @useclawlink/cli actions lumify # list available actions npx -y @useclawlink/cli run lumify --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 Lumify in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Lumify API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Lumify, 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 Lumify is connected in the dashboard, that agent calls the same 10 Lumify 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). ## Lumify MCP for OpenClaw Looking for a Lumify MCP server for OpenClaw? ClawLink connects Lumify to OpenClaw and exposes 10 Lumify 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 Lumify integration](https://claw-link.dev/hermes/lumify) works the same way. ## What the OpenClaw Lumify integration can do 10 Lumify tools are ready for OpenClaw once the account is connected. ### All 10 Lumify tools for OpenClaw | Tool | What it does | |---|---| | **Get credit usage** `lumify_get_credit_usage` | Get the Lumify account tier, usage, limits, trial state, and remaining credits | | **Get event analysis** `lumify_get_event_analysis` | Fetch selected intelligence, odds, odds history, public splits, and/or deterministic stats for | | **Get event score** `lumify_get_event_score` | Get a compact current score and status snapshot for one Lumify event | | **Get events** `lumify_get_events` | Fetch full details for 1-25 event IDs in one API request, optionally including odds or | | **List events** `lumify_list_events` | Find scheduled, live, or historical Lumify events with structured filters and one-page cursor | | **List player events** `lumify_list_player_events` | List one Lumify player's schedule and results with date and status filters, returning one | | **List sports or seasons** `lumify_list_sports_or_seasons` | List Lumify sports and leagues or seasons | | **Plan credit costs** `lumify_plan_credit_costs` | Discover Lumify estimator tool identifiers or estimate credit ranges for up to 50 planned calls | | **Search players** `lumify_search_players` | Search Lumify players by sport, partial name, country, activity, or tennis ranking and return | | **Search teams** `lumify_search_teams` | Search teams by sport, league, conference, division, country, active status, or partial team | ## Example prompts **Get Credit Usage** > Pull the relevant data from Lumify, summarize it in plain English, and point out anything that needs attention. **Get Event Analysis** > Pull the relevant data from Lumify, summarize it in plain English, and point out anything that needs attention. **Get Event Score** > Pull the relevant data from Lumify, summarize it in plain English, and point out anything that needs attention. **Get Events** > Pull the relevant data from Lumify, 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 Lumify working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Lumify API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Lumify 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 Lumify. | 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 Lumify actions to the runtime in a format your agent can reliably use. | 10 tools for Lumify are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Lumify 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 Lumify in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Lumify 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 Lumify skill but can't call the tools The ClawHub skill teaches OpenClaw about Lumify, but the calls run through the ClawLink plugin and your connected account. Make sure Lumify 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 Lumify 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 Lumify tools Lumify 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 Lumify 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. ### Lumify 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 Lumify has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Lumify integration? Yes. ClawLink is the fastest way to connect OpenClaw to Lumify: link your Lumify account once in the browser and OpenClaw can call the Lumify API through 10 ready-made tools — no custom code or token handling. ### How do I add Lumify to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Lumify skill from ClawHub, then you click Connect in the dashboard to authorize Lumify. OpenClaw calls the tools from the next message — no config files, and the Lumify key you paste is stored server-side instead of in your environment. ### How long does it take to connect Lumify to OpenClaw? About two minutes. Sign in, click Connect next to Lumify in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Lumify 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 Lumify working from chat. ### OpenClaw installed the Lumify skill but can't call the tools The ClawHub skill teaches OpenClaw about Lumify, but the calls run through the ClawLink plugin and your connected account. Make sure Lumify 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 - [PostHog tools](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [DataforSEO tools](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [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.