INDIVIDUAL MCP TOOL

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.

tseha.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://tseha.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_components and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tseha-mcp]
url = "https://tseha.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tseha-mcp": {
      "type": "http",
      "url": "https://tseha.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tseha-mcp
Remote MCP URL: https://tseha.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tseha-mcp": {
      "url": "https://tseha.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tseha-mcp": {
      "type": "http",
      "url": "https://tseha.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tseha-mcp",
  "transport": "streamable-http",
  "url": "https://tseha.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

list_projects — Lists the projects in this organization, each with its id, name, and framework.
list_packages — Lists the component packages assigned to a project, each with its name, version, and description, and marks which one is active.
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.
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.
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).
get_style_tokens — Returns the project's design tokens with their names, values, and token paths.
get_standards — Returns the organization's development standards: coding conventions, project structure, and framework-specific rules.
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.