How to connect Mural to OpenClaw
Connect Mural to OpenClaw with ClawLink in one click — 22 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
MuralOAUTH2MCPCollaborative whiteboards and visual workspace for teams. Once connected, OpenClaw can read and act on Mural from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Mural 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 Mural setup: install one ClawHub skill, connect Mural in the browser, and OpenClaw can call real Mural actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Mural skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Mural" (hith3sh/mural) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/mural
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Mural.
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 Mural
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Mural?"
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 Mural in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Mural to authorization request 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Mural is connected in the dashboard, that agent calls the same 22 Mural tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Mural MCP for OpenClaw
Looking for a Mural MCP server for OpenClaw? ClawLink connects Mural to OpenClaw and exposes 22 Mural tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Mural integration works the same way.
What the OpenClaw Mural integration can do
22 Mural tools are ready for OpenClaw once the account is connected.
All 22 Mural tools for OpenClaw
| Tool | What it does |
|---|---|
Authorization request mural_authorization_request | Initiate the OAuth 2.0 authorization process |
Get current user mural_get_current_user | Retrieve information about the currently authenticated user |
Get files for mural mural_get_files_for_mural | Retrieve a list of file widgets in a mural |
Get mural widgets mural_get_mural_widgets | Retrieve all widgets within a specified mural |
Get room mural_get_room | Retrieve information about a specific room by its ID |
Get workspace mural_get_workspace | Retrieve information about a specific workspace by its ID |
Get workspaces mural_get_workspaces | Retrieve all workspaces the authenticated user is a member of |
List folders mural_list_folders | List all folders within a room that the authenticated user has access to |
List open rooms mural_list_open_rooms | List all discoverable open rooms within a workspace |
List recent murals mural_list_recent_murals | List recently opened active murals for the authenticated user in a workspace |
List recent templates mural_list_recent_templates | Retrieve recent templates used by a user for a workspace |
List room murals mural_list_room_murals | List all murals for a room that the authenticated user has read access to |
List room users mural_list_room_users | List all members and guests for a room |
List rooms mural_list_rooms | List all rooms within a workspace |
List tags mural_list_tags | Retrieve all tags in a mural |
List templates mural_list_templates | Retrieve all default templates available in Mural |
List workspace murals mural_list_workspace_murals | List all murals in a workspace that the authenticated user owns or is a member of |
List workspace templates mural_list_workspace_templates | Get default and custom templates for a workspace |
Search murals mural_search_murals | Search for murals within a workspace |
Search rooms mural_search_rooms | Search for rooms within a workspace by name or description |
Search templates mural_search_templates | Search templates within a workspace that the authenticated user owns or has access to |
Create sticky note mural_create_sticky_note | Create one or more sticky note widgets on a mural |
Try it: find the Mural tool you need
Browse the 22 Mural 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 Mural, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Mural, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Mural, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Mural working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Mural app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Mural through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Mural. | 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 Mural actions to the runtime in a format your agent can reliably use. | 22 tools for Mural are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Mural 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 Mural in the browser, and the 22 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Mural skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mural, but the calls run through the ClawLink plugin and your connected account. Make sure Mural 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 Mural 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 Mural tools
Mural 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 Mural 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.
Mural 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Mural and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Mural integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Mural: link your Mural account once in the browser and OpenClaw can call the Mural API through 22 ready-made tools — no custom code or token handling.
How do I add Mural to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Mural skill from ClawHub, then you click Connect in the dashboard to authorize Mural. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Mural to OpenClaw?
About two minutes. Sign in, click Connect next to Mural in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Mural up myself?
The alternative to ClawLink is usually manual OAuth app 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 Mural working from chat.
OpenClaw installed the Mural skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mural, but the calls run through the ClawLink plugin and your connected account. Make sure Mural 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.
