Chrome Course MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chrome_launchB | Launch a Chrome window with the DevTools Protocol enabled, or open a new tab if it is already running. |
| chrome_open_tabA | Open a new tab through an existing Chrome DevTools Protocol endpoint. |
| chrome_tabsA | List Chrome tabs exposed by the local Chrome DevTools Protocol endpoint. |
| chrome_navigateB | Navigate the selected Chrome tab to a URL and wait briefly for the page to load. |
| chrome_snapshotB | Summarize the selected page with visible text, links, buttons, inputs, selects, and forms for automation planning. |
| chrome_clickB | Click an element by CSS selector or visible text. Useful for control panels and file-manager buttons. |
| chrome_typeC | Type into an input or textarea by CSS selector, label text, placeholder, name, id, or aria-label. |
| chrome_selectA | Set a select dropdown by CSS selector or label text, matching option value or visible text. |
| chrome_pressB | Send a keyboard key to the selected page, optionally after focusing an element. |
| chrome_screenshotC | Capture a PNG screenshot of the selected page. |
| chrome_evalB | Evaluate JavaScript in the selected tab. Use for small, explicit inspection or panel automation snippets. |
| chrome_extract_mediaC | Extract media, document, iframe, and link candidates from a selected Chrome tab. |
| coinbase_diagnose_transportB | Passive transport diagnostic for Coinbase real-time data. Attaches before same-tab navigation, observes WS/SSE/poll/WebTransport on page and worker targets, writes a recon network-map + WS TAP VIABLE verdict. Never clicks or opens a Coinbase socket. |
| coinbase_attachA | Attach (fail-closed) to an already-open, already-signed-in Coinbase Advanced Trade tab in the debug profile. Returns { attached, signedIn, tab, probeResults }. Never falls back to an unrelated tab. |
| coinbase_reconA | One-shot deep reconnaissance of the live Advanced Trade page. Writes ./recon/-/ (dom-map.json, network-map.json, behavioral.json, screenshots/, RECON_REPORT.md). Read-only; never submits an order. |
| coinbase_market_streamA | Mirror the page's own Coinbase WebSocket frames over CDP for durationMs, normalize into Tick/L2Update/Trade/Candle (decimal.js), fan out to an in-memory ring buffer + append-only JSONL journal, and detect sequence gaps. Read-only; opens no socket of its own. |
| coinbase_snapshot_stateA | Return the current in-memory ring-buffer state collected by coinbase_market_stream (counts, last tick/trade, recent N events). |
| coinbase_portfolio_snapshotB | Read balances + open orders directly from the Advanced Trade DOM (never from an API), using the discovered selectors with a stability-ranked fallback chain. Read-only. |
| coinbase_place_orderA | EXECUTION SCAFFOLD (dryRun hardcoded true). Validates a would-be order against config risk limits (mode/killSwitch/maxNotionalUsd). OBSERVE_ONLY rejects all; PAPER logs a simulated fill at best bid/ask. NEVER clicks the order form. No real order is ever placed in this pass. |
| coinbase_paper_ledgerA | Read the in-memory PAPER trading ledger: running position, realized/unrealized P&L, recent simulated fills, and advisory half-Kelly sizing from measured PAPER outcomes. Read-only. |
| coinbase_confirm_liveA | Stubbed LIVE ladder third factor. Records an explicit confirmation phrase for audit but never arms or submits live orders. |
| coinbase_reconcile_preview_intentA | Pure preview-vs-intent diff for future safety checks. Accepts intended order fields and a preview-shaped object; performs no clicking or DOM interaction. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Each tool has a clearly distinct purpose within its domain (Chrome automation or Coinbase trading). There is no overlap; descriptions clearly differentiate similar actions like 'chrome_click' and 'chrome_select' or 'coinbase_recon' and 'coinbase_attach'.
All tools follow a consistent prefix_naming convention: 'chrome_verb' for Chrome tools and 'coinbase_verb_noun' for Coinbase tools. The use of snake_case is uniform, and the pattern is predictable across the entire set.
22 tools is on the higher side but still reasonable given the combination of two distinct domains (Chrome automation and Coinbase trading). Each tool serves a specific purpose, though some users might find the Coinbase tools excessive for a 'Chrome Course' server.
The Chrome automation tools cover essential actions (navigation, clicking, typing, JS evaluation, screenshots, tabs), though a few common operations like scrolling are missing. The Coinbase tools provide extensive coverage for trading research (market streaming, portfolio reading, dry-run orders, diagnostics), making the overall surface fairly complete for its intended use.