Tseha is an MCP server with 9 tools an agent can call, among them get_component, get_component_updates, get_standards. It answers at https://tseha.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Serves your design system and coding standards to coding agents, so they stop guessing.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: name, project_id |
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 plann Inputs: current_version, project_id |
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 Inputs: project_id, section, framework |
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 retur Inputs: project_id |
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, Inputs: category, project_id |
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 proj Inputs: project_id |
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 g Inputs: project_id |
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 |
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 Inputs: query, project_id |
Every block below points at https://tseha.io/mcp. Pick your client and copy.
claude mcp add --transport http tseha https://tseha.io/mcp
{
"mcpServers": {
"tseha": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://tseha.io/mcp"]
}
}
}{
"mcpServers": {
"tseha": {
"url": "https://tseha.io/mcp"
}
}
}{
"servers": {
"tseha": {
"type": "http",
"url": "https://tseha.io/mcp"
}
}
}{
"context_servers": {
"tseha": {
"url": "https://tseha.io/mcp"
}
}
}{
"mcpServers": {
"tseha": {
"serverUrl": "https://tseha.io/mcp"
}
}
}{
"mcpServers": {
"tseha": {
"url": "https://tseha.io/mcp"
}
}
}name: Tseha
version: 0.0.1
schema: v1
mcpServers:
- name: Tseha
type: streamable-http
url: https://tseha.io/mcp{
"mcpServers": {
"tseha": {
"httpUrl": "https://tseha.io/mcp"
}
}
}{
"mcpServers": {
"tseha": {
"type": "http",
"url": "https://tseha.io/mcp"
}
}
}{
"mcpServers": {
"tseha": {
"url": "https://tseha.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Ftseha.io%2Fmcp&type=streamable_http&id=tseha&name=Tseha
It answered our last check on 24 October 2026 in 187 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by tseha.io and served from tseha.io, the vendor's own domain: https://tseha.io/mcp.
9, as returned by the server's own tools/list on 22 September 2026: get_component, get_component_updates, get_standards, get_style, get_style_tokens, list_components, list_packages, list_projects, and 1 more.
It answered our last check on 24 October 2026 in 187 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://tseha.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.tseha. Endpoint host: tseha.io. ARD identifier: urn:air:io.tseha:mcp:tseha.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.