get_design_contextLABSCO SUMMARY
The agent reads IDs out of the URL — it never opens the page.
That is why prompting works the way it does: paste a Visily link with a clear intent and the tools resolve the project, board and element from the URL itself. Two things improve the output more than any prompt tweak. Name screens and groups semantically in Visily, because those names flow into both the export and the find-a-board matching. And ask for one screen at a time — the documentation is explicit that smaller selections produce more reliable results.
What it is
The Visily design canvas exposed to coding agents. Point an agent at a Visily board or screen and it can rebuild the UI as real components, find a board from a description, or lift the board's design system as tokens for another app.
What you get
get_design_contextis the primary tool — it returns the design data, theme and screenshot metadata for one elementget_screenshotfetches an image for visual verification against what was generatedget_board_themereturns the board's design system as shadcn tokens in JSON, CSS or Tailwind form- Discovery —
list_workspaces,list_projects,list_boards,list_elementsanswer 'find the board I was working on' - Advanced metadata and raw exports —
get_workspace,get_project,get_board,get_element,get_element_export - Prompts ship with the server —
find_visily_board,generate_code_from_element,apply_board_theme— alongsidevisily://docs/...resources the agent reads on demand - The default generation stack is React + TypeScript + Tailwind v4 + shadcn/ui, rebuilt semantically rather than exported statically
Requirements
A Visily workspace on a Pro or Business plan, where you are the workspace creator or hold an editor licence — free workspaces and viewer or guest roles are not supported, and this is enforced on every request. Authentication is OAuth, prompted by your client on first use; there are no API keys. The server is remote over Streamable HTTP at https://app.visily.ai/api/mcp, published as io.github.visily-app/visily version 0.1.0. Packaged installs exist for Claude Code (claude plugin install visily@visily), Cursor, Codex, Kiro, Antigravity, Replit, Lovable and v0; any other Streamable-HTTP client connects with the URL alone.
Setup effort
Add the hosted endpoint, then sign in — paste it into your client, then approve the OAuth sign-in
USE CASES
Building a screen you have already designed
Give the agent the element link and let it rebuild it as components rather than pasting a static export.
Finding the board you were working on
Describe it and get a link back without leaving the editor.
Applying a design system to an existing app
Pull the board's theme as Tailwind or CSS tokens and apply them instead of hardcoding colours.
Checking the build matches the design
Fetch the screenshot and compare it against what was generated before calling it done.
Reusing your own components rather than new ones
Point the agent at your component directory alongside the design context so it composes from what exists.
12 tools
Listed in project docs. Your client may show a different list.
get_screenshotget_board_themelist_workspaceslist_projectslist_boardslist_elementsget_workspaceget_projectget_boardget_elementget_element_exportBEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
https://app.visily.ai/api/mcpAdd this hosted endpoint to your MCP client, then sign in.
MCP Clients
Claude Code
claude plugin marketplace add visily-app/mcp-plugins
claude plugin install visily@visilyCursor
Cursor 2.5+ packaged plugin, installed from a local clone: run git clone https://github.com/visily-app/mcp-plugins.git, open the cloned folder in Cursor, then run this in the agent chat:
/add-plugin ./plugins/cursorReload Cursor; the server appears under Settings → MCP and asks you to sign in to Visily on first use.
Cline
{
"mcpServers": {
"visily": {
"type": "streamableHttp",
"url": "https://app.visily.ai/api/mcp"
}
}
}Codex
codex plugin marketplace add visily-app/mcp-plugins
codex plugin add visily@visilyVS Code
{
"servers": {
"visily": {
"url": "https://app.visily.ai/api/mcp"
}
}
}Windsurf
{
"mcpServers": {
"visily": {
"serverUrl": "https://app.visily.ai/api/mcp"
}
}
}Other MCP clients
{
"mcpServers": {
"visily": {
"url": "https://app.visily.ai/api/mcp"
}
}
}