01 · Architecture
One contract from source to output
The server reads only versioned files shipped with the package. It does not modify projects, call external services, or collect prompts.
- 01Source filesTokens and component contracts
- 02Nikba MCPDiscoverable, structured context
- 03AI hostImplementation with public APIs
Twenty-three component contracts, five product patterns, two integrations, and six system guides.
Discover, retrieve, filter, and search the installed system without external calls.
The host inspects relevant contracts and tokens before generating interface code.
02 · Resources
Published knowledge
Hosts can discover stable URIs and read the exact documentation included in the installed package.
nikba://system/overviewPrinciples, setup, usage, and the current public surface.
nikba://foundations/tokensPrimitive, semantic, and theme CSS custom properties.
nikba://components/{slug}Purpose, API, variants, states, accessibility, examples, and acceptance criteria for every documented component.
nikba://patterns/{slug}Product compositions, validation, settings, and confirmation guidance.
nikba://integrations/{slug}Lifecycle and ownership boundaries for Livewire and Filament.
nikba://guides/{slug}Foundations, support, release, and migration policy.
03 · Tools
Focused retrieval for AI
Every tool is read only, deterministic for a given package version, and limited to Nikba Design System files.
list_components- Discover component names, descriptions, slugs, and resource URIs.
get_component- Read the complete contract for a component by slug.
list_documents- Discover all documentation or one component, pattern, integration, or guide category.
get_document- Read one complete document by category and slug.
get_tokens- Read all design tokens or one primitive, semantic, or theme layer.
search_design_system- Find relevant guidance across the complete published system.
build_with_nikbaDirects the host to inspect relevant contracts and tokens before implementing an interface.
04 · Connect
Start through standard input and output
Run the server locally, then register its executable in any compatible MCP host.
npm run mcp
{
"mcpServers": {
"nikba-design-system": {
"command": "nikba-design-system-mcp"
}
}
}
The automated test performs a real MCP handshake, discovers capabilities, invokes tools, and reads a resource.