Saymock’s MCP server gives an agent 39 tools to design on a shared board: screens are
HTML with Tailwind CSS v4 classes, the agent checks its own work with renders, handles
the comments people leave, and hands the approved screens over as code. This page lists
them by job, for the people setting up an agent and for agents reading the docs.
Endpoint (Streamable HTTP): https://app.saymock.com/mcp. Sign-in is OAuth in the
browser; clients without OAuth use a personal access token from Settings → Connect your
agent.
Permissions: the agent acts as the person who signed in, in the workspaces they
belong to, with their role in each. A tool given a file uses that file’s workspace.
Hints: every tool declares whether it only reads, may change or delete content,
and reaches outside the account (title, readOnlyHint,
destructiveHint, openWorldHint).
The account the connection acts as, every workspace it reaches with the role in each, and the default workspace.
list_files
The design files of every workspace, most recently edited first, with their pages and screens; searchable by file, page or screen name.
create_file
A new design file, a private draft unless it goes into a project.
get_file
The board’s outline: pages, sections, notes and screens with ids, positions and sizes, without their HTML.
save_version
Saves the file as a named version people can preview and restore (versions are also saved after each editing session).
Creating and editing screens
Tool
What it does
create_frame
A screen on the board, filled with HTML + Tailwind in one call: a device preset (iphone-16, pixel-9, ipad, desktop…) or any size, a height that hugs a long page. It never covers what is already on the board.
edit_html
Rewrites a screen or one element. Elements keep their data-id, so the agent changes one block instead of rewriting the screen.
update_nodes
Patches without HTML: an element’s classes, text, tag or attributes; a template’s rows; a screen’s name, position or size.
delete_nodes
Deletes screens, sections, notes or elements.
make_template
Turns repeated siblings (list rows, cards) into one <template data-each> with a data array: written once, cheaper to edit.
make_component
Makes a block shared between screens (header, tab bar): one main component, instances with props.
detach_instance
Turns an instance back into ordinary elements, to change one screen only.
add_note
A sticky note beside a screen, to explain a decision or behaviour the screen cannot show.
arrange_board
Tidies the board: rows aligned, even spacing, each note beside its screen.
Reading
Tool
What it does
get_html
The HTML of a screen or element with its data-ids; template rows summarized unless asked in full.
find_nodes
Finds elements by text, class, tag, attribute or layer name and returns their ids, one line each, without reading the whole HTML.
Checking its own work
These four tools render the screen in a browser; they count as renders in the
usage limits. Every other tool is unmetered.
Tool
What it does
get_screenshot
A PNG of a screen as the editor draws it; zoom on one element, a slice of a long page, or 2–3× density for details.
check_layout
Measures the rendered screen and lists what a screenshot hides: clipped text, content cut by the edge, off-center icons, unknown icons, broken images, small touch targets.
compare_to_reference
Compares a screen with a reference screenshot: where it differs, the elements that differ most, the move that aligns each one and the reference’s colors.
inspect_reference
Reads exact colors from the reference image: its palette, the color at a point, the main colors of an area.
Alternatives, branches and review
Tool
What it does
propose
A set of alternatives for a screen, kept on that screen: people preview each option in place and choose.
describe_changes
Says what an option changes, numbered on the screen when people preview it.
create_branch
A copy of the file to try a big change; people review it and merge it from the app.
update_branch
Brings the main file’s latest changes into a branch.
request_review
Notifies the person that a branch is ready to review and merge.
Working with the team’s comments
Tool
What it does
list_tasks
The open requests addressed to the agent, each with the element it points at.
wait_for_tasks
Waits for new requests while people review the board, and returns them as soon as they are written.
get_comments
The file’s comment threads, with the element each one is attached to.
reply_comment
Answers in a thread as the agent: in progress, done, or a question; can resolve it.
Two prompts package this: Handle saymock requests (the open requests, once) and
Work session (handle comments live as they are written; /saymock:session
in Claude Code).
From design to code
Tool
What it does
export_code
React (TSX), Vue or standalone HTML with the same Tailwind classes: template rows become a data array and a loop, components get typed props.
get_specs
Implementation specs for any platform (SwiftUI, UIKit, Compose, Views, Flutter, React Native, web): the screen measured as rendered, as an auto-layout tree with sizes, spacing, colors, text styles, icons and states.
Images, fonts, icons and maps
Tool
What it does
list_assets
The workspace’s uploaded fonts (with their Tailwind class) and images (with their URL).
get_upload_url
A signed URL, valid 15 minutes, to upload local files from a shell with curl, without sending them through the conversation.
upload_asset
Uploads an image or a font from a URL, a file attached in the chat, or base64.
update_asset
Renames an asset or fixes a font’s family, weight or style.
delete_asset
Deletes an asset for good.
search_icons
Finds Lucide and Material icons by meaning, or by SF Symbol name with the closest look-alikes.
static_map
A map image with real tiles around a point and optional pins, for a map view or a location card.
Feedback
Tool
What it does
send_feedback
Sends the Saymock team a bug report, an idea or a question on the person’s behalf; the answer comes back in a thread they see in Saymock.