NTV Scaffolding MCP Server
Enables discovery, documentation access, and code generation for NTV Scaffolding Angular components, including templates, TypeScript classes, styles, and tests.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NTV Scaffolding MCP Server show me the documentation for the Button component"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
š¤ NTV Scaffolding MCP Server
MCP (Model Context Protocol) Server for NTV Scaffolding Components - Enables AI assistants to easily discover, understand, and generate code for NTV Scaffolding Angular components.
š Quick Start
Prerequisites
Node.js 18+
npm or yarn
Installation
# Clone or navigate to the project
cd component-mcp
# Install dependencies
npm install
# Build TypeScript
npm run build
# Start the server
npm startš§ Development
# Watch mode (rebuild on changes)
npm run watch
# Run in development mode
npm run devš Available Tools
The MCP Server provides 7 powerful tools for working with NTV components:
1. list_ntv_components
Lists all available NTV Scaffolding components with filtering options.
Parameters:
category(optional): Filter by category (ui, form, navigation, data, layout, utility)
Example:
{
"category": "form"
}2. get_ntv_component_doc
Gets comprehensive documentation for a specific component.
Parameters:
component(required): Component name (e.g., 'Button', 'Input')
Returns:
Component name, selector, category, description
All props with types and defaults
Events, slots, examples
Best practices
3. get_ntv_component_props
Get detailed information about component properties.
Parameters:
component(required): Component namepropName(optional): Specific property to details
Example:
{
"component": "Button",
"propName": "variant"
}4. generate_ntv_template_code
Generates HTML template code for a component with custom configuration.
Parameters:
component(required): Component namevariant(optional): Visual variantsize(optional): Component sizecontent(optional): Content/text insideadditionalProps(optional): Additional propertiesuseConfigPattern(optional): Use config pattern. Default: true
Example:
{
"component": "Button",
"variant": "primary",
"size": "lg",
"content": "Click Me",
"useConfigPattern": true
}5. generate_ntv_component_usage
Generates complete component usage examples with TypeScript class and template.
Parameters:
component(required): Component nameusageType(optional): Type of example (basic, advanced, full-form). Default: basiccomponentName(optional): Custom component name for example
Example:
{
"component": "Button",
"usageType": "advanced",
"componentName": "CustomButton"
}6. generate_ntv_component_file
Generates complete component files (TypeScript, template, styles, tests).
Parameters:
component(required): Component namefilename(optional): Output filename in kebab-caseselector(optional): Angular component selectorincludeStyles(optional): Include CSS file. Default: trueincludeTests(optional): Include test file. Default: true
Example:
{
"component": "Button",
"filename": "my-button",
"selector": "app-my-button",
"includeStyles": true,
"includeTests": true
}7. get_ntv_component_examples
Gets predefined usage examples and code snippets.
Parameters:
component(required): Component nameincludeCode(optional): Include code snippets. Default: true
šļø Project Structure
component-mcp/
āāā src/
ā āāā index.ts # Main MCP server entry point
ā āāā tools/
ā ā āāā index.ts # Tools registry
ā ā āāā listComponents.ts # List components tool
ā ā āāā getComponentDoc.ts # Get documentation tool
ā ā āāā getComponentProps.ts # Get properties tool
ā ā āāā generateTemplateCode.ts # Generate template tool
ā ā āāā generateComponentUsage.ts # Generate usage examples
ā ā āāā generateComponent.ts # Generate component files
ā ā āāā getComponentExamples.ts # Get examples tool
ā āāā data/
ā ā āāā components.ts # Component database
ā āāā resources/
ā āāā index.ts # Resource handlers
āāā dist/ # Compiled output
āāā package.json
āāā tsconfig.json
āāā README.mdš§© Supported Components
The MCP server currently supports:
Button - Versatile button with multiple variants
Input - Form input with validation
Card - Container component
Autocomplete - Input with suggestions
Accordion - Collapsible panels
Stepper - Multi-step workflow
Popover - Contextual tooltip
ThumbnailGallery - Image gallery
Modal - Dialog overlay
Template - Page template layout
š” Use Cases
For AI Assistants:
Discover Components: Use
list_ntv_componentsto see what's availableGet Documentation: Use
get_ntv_component_docfor detailed infoGenerate Code: Use
generate_ntv_template_codefor quick snippetsCreate Examples: Use
generate_ntv_component_usagefor complete examplesGenerate Files: Use
generate_ntv_component_filefor full component files
For Developers:
Quick reference for component APIs
Auto-generation of boilerplate code
Examples and best practices
Type-safe configuration objects
š Integration with Claude/Other AIs
Using with Cursor/Claude:
Start the MCP server:
npm startConfigure your AI client to connect to the server
Ask the AI to use the NTV component tools
The AI can generate components, templates, and code
Example Prompts:
"Show me all available form components"
"Generate a Button component with primary variant and large size"
"Create a complete Button component file with tests"
"Show me advanced usage of the Stepper component"
"Generate a form with Button, Input, and Card components"
š Component Database
The MCP server includes a comprehensive component database (components.ts) with:
Component metadata (name, selector, category)
All properties with types and defaults
Events and slots
Usage examples
Best practices
Configuration interfaces
To add new components:
Edit
src/data/components.tsAdd component metadata to
COMPONENTS_DBarrayRebuild:
npm run buildRestart server:
npm start
š Deployment
Build for production:
npm run buildRun in production:
npm startDocker (Optional):
FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm install --production
COPY dist ./dist
CMD ["npm", "start"]š¤ Contributing
To add new tools:
Create a new file in
src/tools/Implement the
MCPToolinterfaceExport it from
src/tools/index.tsThe tool will automatically be registered
š API Response Format
All tools return responses in this format:
{
"content": [
{
"type": "text",
"text": "response content here"
}
]
}š Troubleshooting
Server won't start:
# Check Node version
node --version # Should be 18+
# Clear cache and reinstall
rm -rf node_modules package-lock.json
npm install
npm run buildTool not found:
Ensure all imports are correct
Verify tool is exported from
tools/index.tsCheck that tool names match exactly
TypeScript errors:
npm run build -- --noEmitš Resources
š License
MIT
šØāš» Author
NTV Scaffolding Team
Happy coding! š
Available Tools
8 toolsgenerate_ntv_component_fileB
Generates a complete TypeScript component file that uses an NTV component
Inputs: component (required), filename, selector, includeStyles, +1 more.
generate_ntv_component_usageC
Generates complete component usage code with TypeScript component class and template
Inputs: component (required), usageType, componentName.
generate_ntv_template_codeC
Generates HTML template code for an NTV component with optional custom configuration
Inputs: component (required), variant, size, content, +2 more.
get_ntv_component_docC
Gets comprehensive documentation for a specific NTV component including props, events, and usage patterns
Inputs: component (required).
get_ntv_component_examplesB
Gets predefined usage examples and code snippets for a specific component
Inputs: component (required), includeCode.
get_ntv_component_propsC
Get detailed information about a component's input properties and configuration options
Inputs: component (required), propName.
get_ntv_component_usage_patternC
Gets the proper Angular standalone component usage pattern for a specific NTV component
Inputs: component (required).
list_ntv_componentsB
Lists all available NTV Scaffolding components with their basic information
Inputs: category.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 8 tools
Most tools have distinct purposes, but there is some overlap between 'get_ntv_component_doc' and 'get_ntv_component_examples' as both provide usage information, which could cause mild confusion. The other tools are clearly differentiated by their specific functions like generation, listing, or property retrieval.
All tools follow a consistent snake_case naming pattern with clear verb_noun structure, such as 'generate_ntv_component_file' and 'get_ntv_component_doc'. This predictability makes it easy for agents to understand and select the right tool based on naming conventions.
With 8 tools, the server is well-scoped for its purpose of scaffolding NTV components, covering generation, documentation, and listing operations. Each tool serves a specific role without feeling excessive or insufficient for the domain.
The toolset provides comprehensive coverage for generating and retrieving component information, but lacks update or delete operations, which are minor gaps since the domain focuses on scaffolding and documentation rather than lifecycle management. Agents can still perform core workflows effectively.
Related MCP Connectors
Serves your design system and coding standards to coding agents, so they stop guessing.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Find UI components and themes, retrieve code, and generate with hosted 21st AI when enabled.
Search @imqueue docs and scaffold typed services & clients from your AI coding agent.