Categories › Software Development › Code search, analysis, refactoring & languages
Serves your design system and coding standards to coding agents, so they stop guessing.
Remote server: your requests and data go to tseha.io. Claude Code: claude mcp add --transport http tseha https://tseha.io/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
list_projects — Lists the projects in this organization, each with its id, name, and framework. Read-only, takes no arguments, and returns only the projectslist_packages — Lists the component packages assigned to a project, each with its name, version, and description, and marks which one is active. Read-only. 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 uget_component — Returns the full specification for one component: import path, props schema, usage example, anti-patterns, when-to-use and when-not-to-use nsearch_components — Searches the components of every package assigned to the project by use case, behavior, or description, and returns up to 10 ranked matches 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 availablget_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 iget_standards — Returns the organization's development standards: coding conventions, project structure, and framework-specific rules. Read-only. Call it beget_component_updates — Returns per-component breaking changes and a migration guide between an installed version of the project's active component package and the Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.