JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 62
  • Score
    100M100P100Q86994F
  • License Apache-2.0

Model Context Protocol server providing Taiga UI documentation search and scaffolding tools.

Package Exports

  • @taiga-ui/mcp
  • @taiga-ui/mcp/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@taiga-ui/mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Taiga UI MCP Server

🚀 The fastest way to integrate Taiga UI components into your AI workflow

A Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to Taiga UI components. Seamlessly retrieve Taiga UI components implementations for your AI-powered development workflow.

Integrate with Your Editor

VS Code

To configure MCP in VS Code with GitHub Copilot, add the taiga-ui server to your project's .vscode/mcp.json configuration file:

{
    "mcpServers": {
        "taiga-ui": {
            "command": "npx",
            "args": [
                "@taiga-ui/mcp@latest",
                "--source-url=https://taiga-ui.dev/llms-full.txt" // or file from "/next" version, if you want
            ]
        }
    }
}

Provided Tools

  1. get_list_components { query?: string }

    • Lists component / section identifiers (with fuzzy substring filtering) along with basic metadata (category, package, type).
    • Input: optional query string to filter IDs (case-insensitive substring).
    • Output: { items: [...], total, query } strictly structured JSON.
{
   "items": [
      { "id": "components/Alert", "name": "Alert", "category": "components", "package": "CORE", "type": "component" }
   ],
   "total": 1,
   "query": null
}
  1. get_component_example { "names": ["...", "..."] }

    • Returns the full markdown content of each resolved section (entire component documentation). Applies fuzzy name resolution (variants: exact, segment, suffix, substring with Tui* variants).
    • Input: { names: string[] } (each >= 2 chars).
    • Output: per name object with id (present only if resolved), package, type, suggestions (only when unresolved), and content (array of code strings when example blocks exist; omitted otherwise). Top-level also includes matched (count of resolved names).
{
   "results": [
      {
         "query": "Alert",
         "id": "components/Alert",
         "package": "CORE",
         "type": "component",
         "content": ["# components/Alert\n- **Package**: ... (full section markdown here)"]
      }
   ],
    "matched": 1
}

Authors

Vladimir Potekhin
Vladimir Potekhin
German Panov
German Panov