How to connect OpenRegister to OpenClaw
Connect OpenRegister to OpenClaw with ClawLink: paste your OpenRegister key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
OpenRegisterAPI KEYMCPOpenRegister provides structured German company, person, ownership, financial, insolvency, document, monitoring, and usage data.. Once connected, OpenClaw can read and act on OpenRegister from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to OpenRegister 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 OpenRegister setup: install one ClawHub skill, connect OpenRegister in the browser, and OpenClaw can call real OpenRegister 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 OpenRegister.
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 OpenRegister
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with OpenRegister?"
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 OpenRegister in the ClawLink dashboard — paste your OpenRegister API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from OpenRegister, 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 OpenRegister is connected in the dashboard, that agent calls the same 10 OpenRegister tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
OpenRegister MCP for OpenClaw
Looking for a OpenRegister MCP server for OpenClaw? ClawLink connects OpenRegister to OpenClaw and exposes 10 OpenRegister tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes OpenRegister integration works the same way.
What the OpenClaw OpenRegister integration can do
10 OpenRegister tools are ready for OpenClaw once the account is connected.
All 10 OpenRegister tools for OpenClaw
| Tool | What it does |
|---|---|
Get company data open_register_get_company_data | Read one company profile, financials, historical ownership, holdings, current owners, or UBOs |
Get credit usage open_register_get_credit_usage | Check the connected OpenRegister account's plan, included and used credits, remaining balance |
Get document open_register_get_document | Fetch an official Handelsregister document in real time for a company or retrieve a stored |
Get insolvency open_register_get_insolvency | Get one insolvency proceeding and its complete published event history, including linked |
Get person data open_register_get_person_data | Read a person's profile and management positions or the companies in which they hold ownership |
List monitors open_register_list_monitors | List every company and person monitor for the connected OpenRegister account, including |
Lookup company by URL open_register_lookup_company_by_url | Resolve a fully qualified company website URL to its OpenRegister company ID and available |
Search companies open_register_search_companies | Find companies by name or structured criteria |
Search insolvencies open_register_search_insolvencies | Search German insolvency proceedings by free text or structured debtor, proceeding, status |
Search people open_register_search_people | Search natural persons by name, birth date, city, or active status |
Try it: find the OpenRegister tool you need
Browse the 10 OpenRegister 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 OpenRegister, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from OpenRegister, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from OpenRegister, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from OpenRegister, 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 OpenRegister working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the OpenRegister API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected OpenRegister 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 OpenRegister. | 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 OpenRegister actions to the runtime in a format your agent can reliably use. | 10 tools for OpenRegister are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes OpenRegister 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 OpenRegister in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the OpenRegister 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 OpenRegister skill but can't call the tools
The ClawHub skill teaches OpenClaw about OpenRegister, but the calls run through the ClawLink plugin and your connected account. Make sure OpenRegister 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 OpenRegister 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 OpenRegister tools
OpenRegister 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 OpenRegister 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.
OpenRegister 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 OpenRegister 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 OpenRegister integration?
Yes. ClawLink is the fastest way to connect OpenClaw to OpenRegister: link your OpenRegister account once in the browser and OpenClaw can call the OpenRegister API through 10 ready-made tools — no custom code or token handling.
How do I add OpenRegister to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink OpenRegister skill from ClawHub, then you click Connect in the dashboard to authorize OpenRegister. OpenClaw calls the tools from the next message — no config files, and the OpenRegister key you paste is stored server-side instead of in your environment.
How long does it take to connect OpenRegister to OpenClaw?
About two minutes. Sign in, click Connect next to OpenRegister in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring OpenRegister 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 OpenRegister working from chat.
OpenClaw installed the OpenRegister skill but can't call the tools
The ClawHub skill teaches OpenClaw about OpenRegister, but the calls run through the ClawLink plugin and your connected account. Make sure OpenRegister 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.
