Koskamo

Tseha MCP MCP server

Tseha MCP serves governed development context, including coding standards, component definitions, architectural rules, and design tokens, to AI coding agents. It ensures agents follow team-specific conventions rather than generic patterns by providing structured, versioned, and queryable engineering knowledge via the Model Context Protocol.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Tseha
MCP endpoint (Streamable HTTP)
https://tseha.io/mcp
Vendor documentation

What you can do with it

  • Query coding standards and architectural rules for an organization
  • Retrieve component details, props, and usage examples
  • Fetch design tokens for styling consistency
  • Search components semantically based on task descriptions
Tools advertised by the last live check:
  • list_projects
  • list_packages
  • list_components
  • get_component
  • search_components
  • get_style
  • get_style_tokens
  • get_standards
  • get_component_updates

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http tseha-mcp https://tseha.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add tseha-mcp --url https://tseha.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tseha-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "tseha-mcp": {
      "url": "https://tseha.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "tseha-mcp": {
      "type": "streamableHttp",
      "url": "https://tseha.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tseha-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "tseha-mcp": {
      "type": "http",
      "url": "https://tseha.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http tseha-mcp https://tseha.io/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "tseha-mcp": {
      "url": "https://tseha.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "tseha-mcp": {
      "serverUrl": "https://tseha.io/mcp"
    }
  }
}

Do you run Tseha MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing