spartan_audit
Generate a verification checklist after installing Spartan components. Checks imports, peer dependencies, Tailwind preset, Brain/Helm pairing, and common setup issues.
LABSCO SUMMARY
Component answers come back matched to your project's versions rather than to a generic doc site.
spartan_project_info and spartan_project_components read the working directory, so which version is installed and which Brain/Helm pairs are half-present are facts rather than assumptions. Source is pulled live from GitHub and spartan_registry_refresh updates the registry from the Spartan Analog API without waiting for a new release of the server. spartan_install_command produces the commands and spartan_audit checks the result, but running them is still yours to do.
What it is
A lookup layer over the Spartan Angular UI library that also reads the Angular or Nx project in your working directory.
What you get
- A component and block listing showing Brain and Helm availability, plus ranked fuzzy search across components, blocks and documentation topics.
- Component detail: Brain directives, Helm components, inputs and outputs, signal models, code examples and installation snippets.
- Dependency graphs — direct, transitive to a depth you choose, and reverse.
- TypeScript source fetched from GitHub for either layer, and block source with its shared utilities and extracted imports.
- Local project detection: Angular version, Nx workspace, Tailwind version, installed Spartan packages, package manager, zoneless mode, and any Brain/Helm pair that is missing its other half.
- Generated install commands with their peer dependencies, a post-install verification checklist, and Spartan skills written into a project's .claude/skills/spartan/ directory.
Requirements
An Angular or Nx project on disk for the tools that read the working directory. A GitHub token in GITHUB_TOKEN is optional: without one the source-fetching tools get 60 GitHub requests an hour, with one 5,000, and it needs no scopes.
Setup effort
One command — npm install -g spartan-ng-mcp
USE CASES
01
Adding a component and finding out what it drags in with it
A component rarely arrives alone. The dependency graph shows the transitive set before the install command is generated for it.
02
Working out why a component looks wrong in this particular project
Half the answers are local: Angular and Tailwind versions, zoneless mode, and Brain components installed without their Helm counterpart.
03
Reading how a component is actually implemented before extending it
Documented inputs and outputs only go so far; the TypeScript source settles what a directive really does.
04
Lifting a page-level block into an application
Blocks come with shared utilities and imports that a copy-paste from a docs page tends to leave behind.
05
Teaching an assistant this library's conventions inside a repo
Composition rules and Brain/Helm patterns are the part an assistant gets wrong most often, and they can be installed into the repository itself.
14 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
spartan_block_source
Fetch the source code of a Spartan page-level block from GitHub. Returns component files, shared utilities, and extracted imports (spartan/angular/cdk/other).
spartan_cache
Manage the MCP server cache. Check status (memory + file stats), clear cached data, or trigger a full rebuild from live sources.
spartan_dependencies
Show the dependency graph for a Spartan component. Returns direct dependencies (which components it needs), transitive dependencies (up to configurable depth), and reverse dependencies (which components depend on it).
spartan_docs
Fetch Spartan documentation topics (installation, CLI, theming, dark-mode, typography, figma, changelog). Returns structured content with code blocks and headings.
spartan_install_command
Generate ready-to-run CLI commands to install Spartan components. Supports Nx generator (recommended) or direct npm install. Returns commands plus required peer dependencies.
spartan_install_skills
Install Spartan Angular UI skills into a project's .claude/skills/spartan/ directory. Skills teach AI assistants how to correctly use Spartan components — Brain/Helm patterns, composition rules, styling conventions. Fetches from GitHub if not available locally.
spartan_list
List all available Spartan Angular UI components and blocks. Components show Brain/Helm availability. Blocks are grouped by category.
spartan_project_components
List Spartan components installed in the current project. Shows Brain/Helm packages with versions and identifies missing pairs (Brain without Helm or vice versa).
spartan_project_info
Detect the Angular/Nx project configuration in the current directory. Returns Angular version, Nx workspace info, Tailwind version, installed Spartan packages, package manager, and zoneless mode status.
spartan_registry_refresh
Refresh the component registry from the live Spartan Analog API. Updates the in-memory registry with the latest components without requiring an MCP update. Shows diff of added/updated/removed components.
spartan_search
Fuzzy search across Spartan components, blocks, and documentation topics. Returns ranked results with relevance scores.
spartan_source
Fetch the TypeScript source code of a Spartan component from GitHub. Returns files from libs/brain/{name}/src/ and/or libs/helm/{name}/src/ with extracted exports.
spartan_view
View detailed information for a Spartan component including Brain directives, Helm components, inputs/outputs, signal models, code examples, and installation snippets.
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools when we connected. Without GITHUB_TOKEN the source-fetching tools are limited to 60 GitHub requests an hour instead of 5000. Five names such as spartan-get-started and spartan-implement are prompts, not tools.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g spartan-ng-mcpMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"spartan-ng": {
"command": "npx",
"args": [
"-y",
"spartan-ng-mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}.mcp.json
Cursor
CURSOR · JSON
{
"mcpServers": {
"spartan-ng": {
"command": "npx",
"args": [
"-y",
"spartan-ng-mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}.cursor/mcp.json
VS Code
VS CODE · JSON
{
"servers": {
"spartan-ng": {
"command": "npx",
"args": [
"-y",
"spartan-ng-mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}.vscode/mcp.json
Any MCP client — from source
Clone the repository and build it
ANY MCP CLIENT — FROM SOURCE · TERMINAL
git clone https://github.com/carlospalacin/spartan-ng-mcp.git
cd spartan-ng-mcp
npm install
npm run buildPoint your client at the build
<YOUR_PATH_TO_SPARTAN_NG_MCP> is the full path of your clone; the build writes dist/index.js. Everything else in your client config stays as in the npx tabs.
ANY MCP CLIENT — FROM SOURCE · JSON
{
"mcpServers": {
"spartan-ng": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SPARTAN_NG_MCP>/dist/index.js"
]
}
}
}
