#Google Chrome MCP

1 messages · Page 1 of 1 (latest)

twilit ferry
#

’m currently running:
Model: openai-codex/gpt-5.4
Agent/runtime: openai-codex
OpenClaw version: 2026.3.13
If you want, I can also give you the full /status-style card.

it’s a missing browser/MCP tool exposure issue.
The problem was basically:
You enabled Chrome remote debugging at 127.0.0.1:9222
But in this session, my available tools still do not include any browser / DevTools MCP tool
So I had no callable tool to attach to Chrome, even though Chrome itself was ready
So the effective error was:
“I can see the endpoint exists, but this runtime does not expose a browser/MCP tool for me to use.”
What I could use here:
web_fetch
web_search (but Brave API key missing)
file/shell/OpenClaw tools
What I couldn’t use here:
any native browser automation / DevTools MCP tool
So yeah — Chrome had the door open, but I wasn’t given the keycard. Very enterprise-core.
TARSX10
6:47

odd bluffBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

crisp sailBOT
#

Yep — there isn’t a separate “DevTools MCP tool” you’re missing. In OpenClaw, Chrome DevTools MCP attach is done through the normal browser tool (with profile="user" / driver existing-session). So if browser isn’t in your tool surface, you effectively can’t use MCP even if Chrome is ready.

Most common cause: your agent is running with a restrictive tool profile (often tools.profile: "coding"), which does not include group:ui → (browser, canvas).

Fix: expose the browser tool to that runtime/session

On the gateway host:

  1. Check what your tool policy is:
openclaw config get tools.profile
openclaw config get tools.allow
openclaw config get tools.byProvider
openclaw config get agents.list
  1. Quick “make it work” test (no restrictions):
# 
openclaw config set tools.profile "full"
openclaw gateway restart
  1. If you do want to stay on the coding profile, add UI tools:
openclaw config set tools.profile "coding"
openclaw config set tools.allow '["group:ui"]' --strict-json
openclaw gateway restart

Important: if you have a tools.byProvider entry for openai-codex / openai-codex/gpt-5.4 that restricts tools, it can still remove browser even if you add it globally — so check that block in particular.

Then test MCP attach (existing session)

Once browser is exposed: