search_screens — Mozaika MCP Tool Read-only
search_screens
(search screens) is one of 23 tools on the
Mozaika
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_screens from your client
- Claude Code Mozaika search_screens run in your project directory
- Claude Desktop Mozaika search_screens ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mozaika search_screens ~/.cursor/mcp.json
- VS Code Mozaika search_screens .vscode/mcp.json
- Zed Mozaika search_screens ~/.config/zed/settings.json
- Windsurf Mozaika search_screens ~/.codeium/windsurf/mcp_config.json
- Cline Mozaika search_screens ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mozaika search_screens ~/.gemini/settings.json
- Grok Mozaika search_screens .mcp.json (in your project root)
- ChatGPT Mozaika search_screens Settings → Connectors → Advanced → Developer mode
- Claude.ai Mozaika search_screens Settings → Connectors → Add custom connector
- LangChain Mozaika search_screens pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mozaika https://mozaika.design/mcpOther tools on this server
- get_screen_sections
- list_user_flows
- get_user_flow
- get_screen
- get_design_system
- get_design_history
- audit_code
- validate_design
- get_web_benchmark
- get_design_drift
- list_design_changes
- get_section
- compare_sections
- get_component
- compare_components
- get_recipe
- compare_recipes
- get_product
- list_my_design_systems
- get_asset_pack
- generate_asset
- get_score
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.