Taiga UI MCP Server

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.

Key Features

• Docs + code snippets. Full Taiga UI markdown plus ready Angular examples in one place.

• Four MCP tools. Get structured overview with get_overview, discover with get_list_components, fetch examples via get_component_example, and access migration guides with get_migration_guide.

• Configurable & lightweight. Pick the docs version (v5 (latest) or v4) without a local Angular install.

Requirements

• Node.js 18 or newer

• VS Code, Cursor, Windsurf, Claude Desktop, Goose or any other MCP client

Getting started

First, install the Taiga UI MCP server with your client.

Quick install

The fastest way is the interactive init command. Run it with no flags to pick the client, the docs version (v5 (latest) or v4), and the scope:

npx @taiga-ui/mcp init

Prefer a one-liner? init writes (or merges) the config into your client's project-local file:

npx @taiga-ui/mcp init --client claude # writes .mcp.json
npx @taiga-ui/mcp init --client cursor # writes .cursor/mcp.json
npx @taiga-ui/mcp init --client vscode # writes .vscode/mcp.json
npx @taiga-ui/mcp init --client windsurf # writes ~/.codeium/windsurf/mcp_config.json (global only)
npx @taiga-ui/mcp init --client opencode # writes opencode.json
npx @taiga-ui/mcp init --client codex # writes .codex/config.toml

Windsurf only reads a machine-global MCP config, so --client windsurf always writes ~/.codeium/windsurf/mcp_config.json regardless of --scope.

Pick the docs version with --version — latest (v5), or a previous major like v4 (defaults to latest):

npx @taiga-ui/mcp init --client cursor --version latest
npx @taiga-ui/mcp init --client cursor --version v4

For a fully custom source, --source-url=... overrides --version.

By default init writes a project-local config you can commit to the repo. Pass --scope user (short -s) to write your machine-global config instead — e.g. ~/.cursor/mcp.json (defaults to project). Pass both with --scope project,user (comma-separated, or repeat the flag) to write the project and global configs in one run:

npx @taiga-ui/mcp init --client cursor --scope user # writes ~/.cursor/mcp.json
npx @taiga-ui/mcp init --client cursor --scope project,user # writes both .cursor/mcp.json and ~/.cursor/mcp.json

Standard config

Prefer manual setup? The standard config works in most of the tools:

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

Removing the server

remove is the inverse of init — it deletes only the taiga-ui entry from a client config, leaving every other server untouched. It accepts the same --client and --scope flags (and the same interactive pickers when omitted):

npx @taiga-ui/mcp remove --client cursor # strips taiga-ui from .cursor/mcp.json
npx @taiga-ui/mcp remove --client codex --scope user # strips it from ~/.codex/config.toml

If the config or the entry is missing, remove reports it and exits successfully.

Tools

1. get_overview

   • Returns structured documentation header: import map (all packages and their exports), code generation checklist, CDK types reference, common mistakes, and getting started guides.

   • Always call this first before using other tools — it provides critical context for correct code generation (right packages, right types, common pitfalls).

   • Output: JSON with sections array (Import Map, Code Generation Checklist, CDK Types Reference, Common Mistakes, Getting Started) and totalComponents count.

get_overview();

{
  "title": "Taiga UI - Complete Documentation",
  "sections": [
    {
      "title": "Import Map - Package Exports Reference",
      "criticalNotices": ["Always import from the correct package. This is the #1 cause of compilation errors."],
      "subsections": [...]
    },
    { "title": "Code Generation Checklist", "subsections": [...] },
    { "title": "CDK Types Reference", "subsections": [...] },
    { "title": "Common Mistakes", "subsections": [...] },
    {
      "title": "Getting Started",
      "description": "Installation and setup guides",
      "subsections": [
        { "title": "addons", "content": ["npm i @taiga-ui/addon-charts ..."] },
        { "title": "app-standalone", "content": ["import {TuiRoot} from '@taiga-ui/core'; ..."] },
        ...
      ]
    }
  ],
  "totalComponents": 185
}

2. 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: strictly structured JSON containing items, total.

get_list_components();

{
  "items": [
    {
        "id": "components/Alert",
        "name": "Alert",
        "category": "components",
        "package": "CORE",
        "type": "component"
    },
    {
      "id": "components/Button",
      "package": "CORE",
      "type": "component",
      "name": "Button",
      "category": "components"
    },
    ...
  ],
}

3. get_component_example { "names": ["...", "..."] }

   • Returns full markdown content for each resolved section (entire component documentation).

   • Fuzzy name resolution: exact match, path segment, suffix, substring, and Tui* variants.

   • Input: { names: string[] } (each name length ≥ 2).

   • Output: results array with objects: query, id (if resolved), package, type, suggestions (only when unresolved), content (array of code blocks, if examples exist). Top-level also includes matched (count of resolved names).

get_component_example({names: ['Alert']});

{
  "results": [
    {
      "query": "Alert",
      "id": "components/Alert",
      "package": "CORE",
      "type": "component",
      "content": ["# components/Alert\n- **Package**: ... (full component API, usage examples, ...)"]
    }
  ],
  "matched": 1
}

4. get_migration_guide

   • Returns the complete Migration Guide for Taiga UI version updates with pre-update checklist, migration instructions via schematics, and troubleshooting for common issues.

   • Use this tool when you need to migrate between Taiga UI major versions or understand the migration process.

   • Input: none (no parameters required).

   • Output: title, introduction with version info, and sections array with migration guidance, code blocks for CLI commands, and solutions for common problems.

get_migration_guide();

{
  "title": "Migration Guide",
  "introduction": [
    "**Guide to update Taiga UI v{CURRENT_MAJOR} -> v{NEXT_MAJOR}**"
  ],
  "sections": [
    {
      "title": "Before You Update",
      "content": [...]
    },
    {
      "title": "Updating",
      "content": [...],
      "codeBlocks": [...]
    },
    {
      "title": "Troubleshooting",
      "content": [...]
    }
  ]
}

Tip: Start with get_overview to get import map and common mistakes, then use get_list_components to discover IDs, get_component_example to fetch full implementation snippets, and get_migration_guide for version upgrade guidance.

Maintained

Taiga UI MCP is a part of Taiga UI libraries family which is backed and used by a large enterprise. This means you can rely on timely support and continuous development.

Authors