# How to connect Memberspot to OpenClaw (paste one key, 13 tools) > Connect Memberspot to OpenClaw with ClawLink: paste your Memberspot key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/memberspot The usual route to Memberspot 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 Memberspot setup: install one ClawHub skill, connect Memberspot in the browser, and OpenClaw can call real Memberspot 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 Memberspot. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Memberspot** — 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 memberspot # connect Memberspot (browser OAuth) npx -y @useclawlink/cli actions memberspot # list available actions npx -y @useclawlink/cli run memberspot --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 Memberspot in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Memberspot API key once. Verify the connection by asking OpenClaw: > Use Memberspot to find user by mail 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 Memberspot is connected in the dashboard, that agent calls the same 13 Memberspot 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). ## Memberspot MCP for OpenClaw Looking for a Memberspot MCP server for OpenClaw? ClawLink connects Memberspot to OpenClaw and exposes 13 Memberspot 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 Memberspot integration](https://claw-link.dev/hermes/memberspot) works the same way. ## What the OpenClaw Memberspot integration can do 13 Memberspot tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 13. ### 11 of 13 Memberspot tools for OpenClaw | Tool | What it does | |---|---| | **Find user by mail** `memberspot_find_user_by_mail` | Retrieve a user's details by their email address | | **Get user course progress** `memberspot_get_user_course_progress` | Retrieve user course progress for a specific course and email | | **List custom user properties** `memberspot_list_custom_user_properties` | List all defined custom user properties | | **List offers** `memberspot_list_offers` | Retrieves all available offers (products/course bundles) from the Memberspot school | | **List user course progress** `memberspot_list_user_course_progress` | Retrieves paginated list of all course progress for a specific user by email | | **List users** `memberspot_list_users` | List all users in your Memberspot school with optional filtering and pagination | | **Create login token** `memberspot_create_login_token` | Generate a one-hour login token for a user | | **Grant user offer by mail** `memberspot_grant_user_offer_by_mail` | Grant a user access to an offer by email | | **Set offer expires** `memberspot_set_offer_expires` | Set or remove the expiration date for an offer for a user | | **Set user offer state** `memberspot_set_user_offer_state` | Revoke or set the state of a specific offer for a user | | **Set order state** `memberspot_set_order_state` | Manages order-based offer access for a user in Memberspot | ## Example prompts **Find User By Mail** > Use Memberspot to find user by mail and walk me through the result in plain English. **Get User Course Progress** > Pull the relevant data from Memberspot, summarize it in plain English, and point out anything that needs attention. **List Custom User Properties** > List the relevant items in Memberspot, group them by priority, and recommend what OpenClaw should do next. **List Offers** > List the relevant items in Memberspot, 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 Memberspot working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Memberspot API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Memberspot 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 Memberspot. | 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 Memberspot actions to the runtime in a format your agent can reliably use. | 13 tools for Memberspot are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Memberspot 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 Memberspot in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Memberspot 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 Memberspot skill but can't call the tools The ClawHub skill teaches OpenClaw about Memberspot, but the calls run through the ClawLink plugin and your connected account. Make sure Memberspot 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 Memberspot 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 Memberspot tools Memberspot 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 Memberspot 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. ### Memberspot 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 Memberspot has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Memberspot integration? Yes. ClawLink is the fastest way to connect OpenClaw to Memberspot: link your Memberspot account once in the browser and OpenClaw can call the Memberspot API through 13 ready-made tools — no custom code or token handling. ### How do I add Memberspot to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Memberspot skill from ClawHub, then you click Connect in the dashboard to authorize Memberspot. OpenClaw calls the tools from the next message — no config files, and the Memberspot key you paste is stored server-side instead of in your environment. ### How long does it take to connect Memberspot to OpenClaw? About two minutes. Sign in, click Connect next to Memberspot in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Memberspot 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 Memberspot working from chat. ### OpenClaw installed the Memberspot skill but can't call the tools The ClawHub skill teaches OpenClaw about Memberspot, but the calls run through the ClawLink plugin and your connected account. Make sure Memberspot 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 - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](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.