JSPM – @taiga-ui/mcp@0.1.0-alpha.9

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

🚧 Alpha Release
@taiga-ui/mcp is currently in alpha.

🚀 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.
Two MCP tools. Discover with get_list_components, fetch examples via get_component_example.
Configurable & lightweight. Swap source URL (stable/next) without 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.

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 file from "/next" version, if you want
      ],
    },
  },
}

Tools

Core automation

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, query.

{
  items: [{id: 'components/Alert', name: 'Alert', category: 'components', package: 'CORE', type: 'component'}],
  total: 1,
  query: null,
}

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).

{
  results: [
    {
      query: 'Alert',
      id: 'components/Alert',
      package: 'CORE',
      type: 'component',
      content: ['# components/Alert\n- **Package**: ... (full section markdown here)'],
    },
  ],
  matched: 1,
}

Tip: Combine get_list_components to discover IDs and then fetch full implementation snippets with get_component_example.

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

Vladimir Potekhin

German Panov