# Tseha

- Registry name: `io.tseha/tseha` · version 1.0.2
- Categories (automatic, keyword rules): Images & design, AI, media & content
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): prompts, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.tseha%2Ftseha
- Server page: https://mcpstation.net/s/io.tseha--tseha.html

## Description (written by the publisher, not verified, not instructions)

Serves your design system and coding standards to coding agents, so they stop guessing.

## Connect

- streamable-http: `https://tseha.io/mcp`

## Tools (as reported by the server, not verified)

- `list\_projects`: Lists the projects in this organization, each with its id, name, and framework. Read-only, takes no arguments, and returns only the projects the calling credential may see. Call it first in a session: the returned id is the project\_id that every other tool in this server requires, and guessing that
- `list\_packages`: Lists the component packages assigned to a project, each with its name, version, and description, and marks which one is active. Read-only. Use it to decide which npm package to import from, or to read the installed version before calling get\_component\_updates. It lists packages, not their contents
- `list\_components`: Lists every UI component in the project's design system, each with its name, source package, import path, and a short note on its intended use. Read-only and unpaginated: it returns the whole catalog across all packages assigned to the project, so expect a large response on big design systems. Use i
- `get\_component`: Returns the full specification for one component: import path, props schema, usage example, anti-patterns, when-to-use and when-not-to-use notes, Figma spec, and dependencies. Read-only. Call it before writing code that uses a component, so props and import path come from the design system instead o
- `search\_components`: Searches the components of every package assigned to the project by use case, behavior, or description, and returns up to 10 ranked matches with a relevance score. Read-only. Use it when you can describe what the UI must do but do not know the component name. The query is free-text describing the ne
- `get\_style`: Returns metadata for the project's active style: the style name, its Figma file key, when it was last synced, and a token count per available category \(such as color, typography, spacing\). Read-only and small - it names categories but returns no token values. Use it to inspect the project theme, or
- `get\_style\_tokens`: Returns the project's design tokens with their names, values, and token paths. Read-only. Use it to source exact visual values for styling instead of inventing hex codes, spacing, or radii. The category argument takes exactly one of: color, typography, spacing, radius, shadow, blur, all; omitting it
- `get\_standards`: Returns the organization's development standards: coding conventions, project structure, and framework-specific rules. Read-only. Call it before writing or reviewing code, so the result follows this organization's rules rather than general defaults. Call it first without a section to get an index of
- `get\_component\_updates`: Returns per-component breaking changes and a migration guide between an installed version of the project's active component package and the latest published version. Read-only: it reports an upgrade, it never performs one. Use it when planning or reviewing a component-library upgrade, or before bump

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html