How to connect Noloco to OpenClaw
Connect Noloco to OpenClaw with ClawLink: paste your Noloco key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine.
NolocoAPI KEYMCPNoloco is a no-code platform for building internal tools, client portals, and business applications backed by a dynamic GraphQL data API.. Once connected, OpenClaw can read and act on Noloco from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Noloco 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 Noloco setup: install one ClawHub skill, connect Noloco in the browser, and OpenClaw can call real Noloco 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 Noloco.
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 Noloco
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Noloco?"
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 Noloco in the ClawLink dashboard — paste your Noloco API key once.
Verify the connection by asking OpenClaw:
Use Noloco to describe table 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 Noloco is connected in the dashboard, that agent calls the same 7 Noloco tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Noloco MCP for OpenClaw
Looking for a Noloco MCP server for OpenClaw? ClawLink connects Noloco to OpenClaw and exposes 7 Noloco tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Noloco integration works the same way.
What the OpenClaw Noloco integration can do
7 Noloco tools are ready for OpenClaw once the account is connected. The 6 below are the ones people reach for most; your agent can call all 7.
6 of 7 Noloco tools for OpenClaw
| Tool | What it does |
|---|---|
Describe table noloco_describe_table | Describe one Noloco table's selectable fields, unique lookup selectors, filters, and |
Get record noloco_get_record | Fetch one record from a Noloco table by a supported unique selector |
List records noloco_list_records | Return one forward-paginated page of records from a table in the connected Noloco app |
List tables noloco_list_tables | List the record tables and generated CRUD operation names available in the connected Noloco app |
Create record noloco_create_record | Create one record in a table in the connected Noloco app |
Update record noloco_update_record | Partially update one Noloco record by ID |
Try it: find the Noloco tool you need
Browse the 6 Noloco tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Noloco to describe table and walk me through the result in plain English.
Pull the relevant data from Noloco, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Noloco, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Noloco, 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 Noloco working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Noloco API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Noloco 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 Noloco. | 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 Noloco actions to the runtime in a format your agent can reliably use. | 7 tools for Noloco are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Noloco 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 Noloco in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Noloco 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 Noloco skill but can't call the tools
The ClawHub skill teaches OpenClaw about Noloco, but the calls run through the ClawLink plugin and your connected account. Make sure Noloco 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 Noloco 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 Noloco tools
Noloco 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 Noloco 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.
Noloco 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 Noloco 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 Noloco integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Noloco: link your Noloco account once in the browser and OpenClaw can call the Noloco API through 7 ready-made tools — no custom code or token handling.
How do I add Noloco to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Noloco skill from ClawHub, then you click Connect in the dashboard to authorize Noloco. OpenClaw calls the tools from the next message — no config files, and the Noloco key you paste is stored server-side instead of in your environment.
How long does it take to connect Noloco to OpenClaw?
About two minutes. Sign in, click Connect next to Noloco in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Noloco 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 Noloco working from chat.
OpenClaw installed the Noloco skill but can't call the tools
The ClawHub skill teaches OpenClaw about Noloco, but the calls run through the ClawLink plugin and your connected account. Make sure Noloco 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.
