You can connect Local Dominator to OpenClaw, the open-source, self-hosted AI agent runtime, by adding our connector through OpenClaw’s MCP manager. This gives your agent direct, read-only access to your SERP Tracker, Site Audit, Geogrid, AI Tracker, and Review Velocity data, so you can ask for reports and analysis in plain English instead of exporting CSVs or switching tabs.
🎯 Who is this for?
This is for agencies and technical teams already running OpenClaw as their self-hosted agent runtime who want live Local Dominator data available inside it without leaving the app.
- Agencies running OpenClaw on their own server, NAS, or VPS
- Technical users comfortable with a terminal (OpenClaw’s setup is CLI-first)
📋 What you will need
You need OpenClaw installed and running, and your Local Dominator API key. There’s nothing to download separately. OpenClaw fetches and runs the connector automatically the first time it connects.
-
OpenClaw installed
(openclaw.ai one-line installer)
Works with Node.js 22+
curl -fsSL https://openclaw.ai/install.sh | bash - Your Local Dominator API key, from your account’s API settings page.
-
No separate download needed.
OpenClaw runs Local Dominator’s official connector directly from our
hosted connector file via
npx, so there are no files to create or manage yourself.
⏳ Time to complete
- ~ 10 minutes
How to Connect OpenClaw
Log into Local Dominator, go to account/API settings, and copy your key.
ld_
Keep your API key private. Treat it like a password—never share it in chat, email, or a screenshot.
Run the following command in your terminal.
openclaw mcp set local-dominator '{"command":"npx","args":["-y","https://localdominator.co/wp-content/uploads/2026/08/LOCAL-1.tgz"],"env":{"LOCAL_DOMINATOR_API_KEY":"ld_your_actual_key_here"}}'
Replace
ld_your_actual_key_here
with your real Local Dominator API key.
mcp set works across OpenClaw CLI
versions, including older installs.
You can use the newer
openclaw mcp add
command instead.
openclaw mcp add local-dominator --command npx --arg "-y" --arg "https://localdominator.co/wp-content/uploads/2026/08/LOCAL-1.tgz" --env "LOCAL_DOMINATOR_API_KEY=ld_your_actual_key_here"This command additionally proposes the connection before saving.
Run this command to view the saved connector configuration.
openclaw mcp show local-dominatorThis prints the saved config so you can double-check that the key and repository name are correct.
Test the connection by requesting live Local Dominator data.
mcp set only writes the configuration.
It does not test whether the connector can successfully communicate with
Local Dominator.
What You Can Ask For
Once connected, your agent can pull and summarize live data on request. You don’t need to know tool names or campaign IDs in advance—just describe what you want.
Check my Local Dominator account status.Pull the SERP campaign for [client domain] and tell me which keywords dropped this week.List open critical site audit issues for [site] and draft a client-ready summary.What’s our AI Tracker visibility trend for [brand] over the last 30 days?Show me the latest GeoGrid scan results for [business name].Troubleshooting and FAQ
“Command not found” or
mcp add doesn’t recognize
--command,
--arg, or
--env
You’re using an older OpenClaw CLI. Use the
mcp set command from
Step 2
instead. It is the more broadly compatible option.
Asking the agent for account status doesn’t return data
Run the following command to confirm that the configuration was saved with the correct API key and repository name:
openclaw mcp show local-dominatorIf the configuration looks correct but still doesn’t respond, confirm that the OpenClaw process has outbound internet access to reach localdominator.co .
npx fetch.
“LOCAL_DOMINATOR_API_KEY is not set” or authentication errors
Recheck the API key value by running:
openclaw mcp show local-dominatorA copy-and-paste error in the JSON is the most common cause.
Tool calls ask for approval every time
Approval behavior depends on your installation’s execution policy. Run the following command to see your current settings, including the security level and whether prompts are enabled:
openclaw approvals get
Some installations, especially headless or bot-driven ones, already run
with prompts disabled by default. If yours prompts and you want to
always allow this connector, first find your
npx path:
which npx
npx is frequently a symlink
rather than the actual binary. For example,
which npx might return
/usr/local/bin/npx, while the
file it points to may be:
Check both paths with:
which npx
realpath $(which npx)Allowlist both paths because it is not guaranteed which path OpenClaw’s approval matcher checks. Having both entries costs nothing:
openclaw approvals allowlist add --agent "*" "/usr/local/bin/npx"
openclaw approvals allowlist add --agent "*" "/usr/local/lib/node_modules/npm/bin/npx-cli.js"which and
realpath commands. The paths
above are examples and may be different on your machine.
This allowlists by binary path, not by MCP server name, so it applies
to any npx-run command—not only
this connector.
After adding both paths, ask the agent for account status again to confirm that the approval prompt no longer appears.