Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MIRO_BRIDGE_PORTNoPort used by the local bridge (default 7788). Set this (and the app URL) to a free port if the default port is used by another program.
MIRO_BRIDGE_INSTALL_URLNoInstallation URL of your own Miro app, used instead of the maintainer's install link when hosting your own Miro app.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_board_infoA

Cheap overview: board id, item counts by type, frames {id, title, children}, and whether the user set a focus. Call this first instead of reading the whole board, then get_focus or get_items with parentId.

get_itemsA

List board items, filtered by type, ids and/or parentId (a frame id). Items come back compact: {id, type, content/title as plain text, x, y, width, height, parentId, fill (= style.fillColor), from/to (connector ends)}. x/y of an item with parentId are relative to the frame top-left. Pass full:true only if you need raw Web SDK fields.

get_focusA

Items the user marked as focus (select on the board + click the MiroBridgeMCP icon), including everything inside focused frames. Focus is the part of the board the user is working on now: start from it and prefer it, but it is not a boundary; read or reference other items when the task needs them (old ideas, related frames). Compact items.

set_focusA

Set the focus to these ids (frames include their children), or [] to clear. Focus is the part of the board the user is working on now: start from it and prefer it, but it is not a boundary; read or reference other items when the task needs them (old ideas, related frames).

get_selectionB

Items the user currently has selected on the board (compact).

create_itemsB

Create one or many items in one call. Each entry is {type, props}; props are Web SDK create props, e.g. sticky_note {content:"hi", x, y, style:{fillColor:"light_yellow"}}; shape {shape:"rectangle", content, x, y, width, height, style:{fillColor, borderColor, borderWidth, color, fontSize, textAlign}} (shape: rectangle, round_rectangle, circle, triangle, rhombus, parallelogram, trapezoid, pentagon, hexagon, octagon, star, cross, cloud, can, wedge_round_rectangle_callout, right_arrow, left_arrow, left_right_arrow, left_brace, right_brace, flow_chart_predefined_process; other flow_chart_* names (process, decision, terminator, document, ...) are tried through Miro's experimental API); text {content, x, y}; frame {title, x, y, width, height}; connector {start:{item:id, snapTo:"right"}, end:{item:id, snapTo:"left"}, shape:"curved"|"straight"|"elbowed", style:{strokeColor:"#1a1a1a", strokeWidth:2, strokeStyle:"dashed", startStrokeCap:"none", endStrokeCap:"arrow"}, captions:[{content}]} (snapTo: auto|top|right|bottom|left); card {title, description, x, y}; image {url, x, y} or {path:"C:/local/file.png", x, y, width} or {svg:"...", x, y} (svg = drawings / freehand strokes); embed {url, x, y}. Add parentId to place the item inside a frame (x/y here are still board coordinates). Returns created items (compact).

update_itemsA

Update items: each entry is {id, props}; props are merged into the item (nested style is merged too) then synced. props.parentId: a frame id moves the item into that frame (it must lie inside the frame), null takes it out. Returns updated items (compact).

arrange_itemsA

Auto-layout items into a tidy grid/row/column (uniform cells = largest item, gap between). Give ids (kept in that order) or parentId (all items in that frame, current reading order). Connectors are skipped; they follow their items. Starts at the current top-left of the items. Returns {moved, columns}.

delete_itemsA

Delete items by id. Deleting an item also deletes connectors attached to it; ids already gone are counted in alreadyGone.

zoom_toB

Move the viewport so the given items are visible.

group_itemsB

Group items (ids) so they move together, or ungroup a group (ungroupId). Returns the group, or the freed item ids.

reorder_itemsB

Bring items to the front or send them to the back (z-order), e.g. text hidden behind a shape.

create_tableA

Draw a table as a grid of rectangle shapes, grouped. Native Miro tables cannot be created or read through the Web SDK (they show up as type "unsupported"; read one with capture). rows[0] is the header when header is true. x/y = top-left (board coordinates). cells are ids row by row; edit a cell with update_items.

captureA

Screenshot of the Miro window so you can see the result. Optionally zoom to ids first. Windows only; the board window must not be minimized (it may be behind others). ~1.5k tokens per image, so capture once after a batch of changes, not after every call.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have a clear distinct purpose (read vs. create vs. delete vs. mutate vs. viewport), and descriptions add helpful cues like 'z-order' for reorder_items vs. 'auto-layout' for arrange_items. Two mild overlaps remain: get_selection and get_focus both return user-selected items, and reorder_items/arrange_items could be confused at a glance despite the clarifying text.

Naming Consistency4/5

Nearly all tools follow a snake_case verb_object pattern (get_items, create_items, update_items, delete_items, group_items, set_focus, get_board_info). Minor deviations: 'capture' is a bare verb with no object, and 'zoom_to' uses a verb+preposition form that breaks the pattern slightly.

Tool Count5/5

14 tools sit comfortably in the well-scoped range, and each one maps to a distinct board operation: reading (items, focus, selection, board info), mutation (create/update/delete/group/reorder/arrange), plus capture and zoom_to for visual feedback. Nothing looks redundant or missing for the stated Miro workflow purpose.

Completeness4/5

The surface covers the full lifecycle — create (including bulk, tables, images, connectors), read (compact and via board info/focus/selection), update, delete, plus grouping, z-order, auto-layout, viewport and screenshot verification — so agents won't hit dead ends. The main gap is native Miro tables being unreadable except via the capture workaround, and no direct single-item fetch beyond filtering get_items by id.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues