stitch-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STITCH_API_KEY | No | Stitch API key (recommended) | |
| STITCH_ACCESS_TOKEN | No | Alternative: OAuth access token |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all Stitch projects accessible to the user. |
| create_projectB | Create a new Stitch project (container for UI designs). |
| generate_screenA | Generate a new UI screen from a text prompt. Returns the screen ID and full HTML content. |
| edit_screenB | Edit an existing screen using a text prompt. Returns updated screen ID and HTML. |
| generate_variantsA | Generate 1-5 design variants of an existing screen. Returns array of screen IDs and HTML. |
| list_screensB | List all screens in a Stitch project. |
| get_screen_htmlA | Get the full HTML content of a screen. Returns the actual HTML code, not just a URL. |
| get_screen_imageA | Get a screenshot of a screen as base64-encoded image. |
| build_siteA | Build a multi-page site from a project by mapping screens to URL routes. Returns HTML for each page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource-action pair: projects vs screens, and create/edit/list/get/build each have clear separation. No two tools appear to do the same thing, even generate_screen and edit_screen are differentiated by new vs existing.
All tool names follow a consistent verb_noun snake_case pattern (list_projects, create_project, generate_screen, edit_screen, etc.). The naming is predictable and uniform across the entire set.
With 9 tools, the set is well-scoped for a UI design/build server. Each tool covers a necessary operation without redundancy or bloat, fitting comfortably in the ideal 3-15 range.
The set covers core lifecycle operations for projects and screens, including creation, retrieval, editing, and site building. Minor gaps exist, such as no delete operations for projects or screens, but these are workaround-able and not critical for the primary workflow.