browsercard-live

Skill: browsercard-live

Work with a live, running BrowserCard instance via the BrowserCard-AIBroker MCP server.

---

See also: browsercard-reference skill — full widget property reference and complete scripting API (apply it alongside this skill to avoid exploratory widget_get calls).

Prerequisites

The MCP server (BrowserCard-AIBroker) must be running and BrowserCard must be open in a browser tab. The server exposes 30 tools. All tools except connection_status require an active connection.

---

Step 1 — Check connection

Always start with connection_status before any other tool call.

connection_status()

• connected: true → proceed
• connected: false → tell the user to open BrowserCard and connect via "Deck menu → MCP Settings…", then retry

The response also gives deck_name and current_card — use them for orientation.

---

Step 2 — Understand the deck structure

Before making any changes, build a mental model of the deck:

deck_get()              → deck metadata (name, dimensions, grid, script)
list_cards()            → all cards with id, name, widget count, has_script
list_widgets(card_id)   → all widgets on a card with id, name, type, position

Only call list_widgets for cards you actually need to work on. Do not dump all cards upfront.

---

Tool reference

Connection (group 1)

Tool	Description
connection_status	Connection state, deck name, current card. Works without BC.

Deck (group 2)

Tool	Key params
deck_get	—
deck_patch	props: DeckProps
deck_save	— (persists to IndexedDB)

DeckProps (all optional): Name, readOnly, swipeToAdjacentCard, Script, CardWidth, CardHeight, SnapToGrid, GridWidth, GridHeight

Navigation (group 3)

Tool	Key params
list_cards	—
list_widgets	card_id
find	query: FindQuery

FindQuery (all optional): scope (cards/widgets/all), namePattern, widgetType, valueContains, scriptContains