How to connect Glasp to OpenClaw
Connect Glasp to OpenClaw with ClawLink: paste your Glasp key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
GlaspAPI KEYMCPGlasp helps users save bookmarks, capture and organize highlights, import Kindle highlights, and access AI-generated summaries.. Once connected, OpenClaw can read and act on Glasp from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Glasp 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 Glasp setup: install one ClawHub skill, connect Glasp in the browser, and OpenClaw can call real Glasp 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 Glasp.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Glasp
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Glasp?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Glasp in the ClawLink dashboard — paste your Glasp API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Glasp, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Glasp is connected in the dashboard, that agent calls the same 9 Glasp tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Glasp MCP for OpenClaw
Looking for a Glasp MCP server for OpenClaw? ClawLink connects Glasp to OpenClaw and exposes 9 Glasp tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Glasp integration works the same way.
What the OpenClaw Glasp integration can do
9 Glasp tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9.
8 of 9 Glasp tools for OpenClaw
| Tool | What it does |
|---|---|
Get summary glasp_get_summary | Fetch one Glasp summary by ID, optionally including the stored page or PDF Markdown content |
List bookmarks glasp_list_bookmarks | Return one page of pages the connected user saved to Glasp without highlighting, optionally |
List highlights glasp_list_highlights | Return one page of the connected user's non-Kindle Glasp documents and their nested highlights |
List kindle highlights glasp_list_kindle_highlights | Return one page of the connected user's read-only Kindle books and highlights imported into |
List summaries glasp_list_summaries | Return one page of AI summaries generated by the connected user for pages, PDFs, and YouTube |
Create highlights glasp_create_highlights | Create between 1 and 100 highlights in the connected Glasp account in one request |
Save bookmark glasp_save_bookmark | Save a URL as a Glasp bookmark, or update the existing bookmark when that URL is already saved |
Update highlight glasp_update_highlight | Update editable fields on one Glasp highlight identified by its source URL and highlight ID |
Try it: find the Glasp tool you need
Browse the 8 Glasp tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Glasp, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Glasp, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Glasp, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Glasp, 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 Glasp working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Glasp API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Glasp 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 Glasp. | 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 Glasp actions to the runtime in a format your agent can reliably use. | 9 tools for Glasp are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Glasp 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 Glasp in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Glasp key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Glasp skill but can't call the tools
The ClawHub skill teaches OpenClaw about Glasp, but the calls run through the ClawLink plugin and your connected account. Make sure Glasp 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 Glasp 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 Glasp tools
Glasp 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 Glasp 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.
Glasp 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 Glasp has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Glasp integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Glasp: link your Glasp account once in the browser and OpenClaw can call the Glasp API through 9 ready-made tools — no custom code or token handling.
How do I add Glasp to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Glasp skill from ClawHub, then you click Connect in the dashboard to authorize Glasp. OpenClaw calls the tools from the next message — no config files, and the Glasp key you paste is stored server-side instead of in your environment.
How long does it take to connect Glasp to OpenClaw?
About two minutes. Sign in, click Connect next to Glasp in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Glasp 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 Glasp working from chat.
OpenClaw installed the Glasp skill but can't call the tools
The ClawHub skill teaches OpenClaw about Glasp, but the calls run through the ClawLink plugin and your connected account. Make sure Glasp 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
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
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.