next-ui-mcp
Related Servers
Alternatives to next-ui-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables developers using agentic AI tools to scaffold applications and integration cards, retrieve API references and best-practice guidelines, inspect project metadata, validate manifests, and detect and fix framework-specific code issues.289 npmMIT
- AlicenseAqualityAmaintenanceEnables natural language interaction with ServiceNow Fluent SDK commands, API specifications, and development resources for AI-assisted environments.17132 npm31MIT
- FlicenseAqualityDmaintenanceEnables AI agents to query component governance rules, validate component props, and generate development prompts for questionnaire editors.4-
- AlicenseNot gradedqualityBmaintenanceEnables Claude and other MCP clients to perform real ServiceNow development across multiple instances: running server-side scripts, debugging ACLs, flows, notifications and ATF tests, tracing impact and change history, and migrating update sets through export, preview and commit.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and development tools to interact with ServiceNow instances through the Model Context Protocol, supporting incident, change, problem, CMDB, service catalog, knowledge base, and custom table operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and development tools to interact with ServiceNow instances through a standardized interface, supporting comprehensive API coverage for incident, change, CMDB, and more.MIT
TDQS
Scored across 11 tools
Several tools cluster around component discovery: search_instance_components ('group likely platform components') and recommend_instance_components ('recommend likely HDS components from a curated registry') are nearly indistinguishable, and resolve_component_package/evaluate_platform_component_fit/get_component_api further overlap in the same decision space. Most other tools (guidance, scaffold, manifest validate vs explain, icon search) are clearly distinct, so descriptions help but boundaries are fuzzy.
Every tool follows a clean snake_case verb_noun pattern (get_framework_guidance, validate_now_ui_manifest, search_instance_icons, evaluate_platform_component_fit, etc.). No mixed conventions or vague bare verbs.
11 tools is a sensible, well-scoped set for a component-development assistant. Slightly heavy on overlapping discovery/decision helpers, but each has a plausible place.
Covers the lifecycle well: guidance, scaffolding, manifest explain/validate, icon lookup, component discovery, API inspection, dependency analysis, and platform-fit decisions. Minor gap in that manifest authoring is only indirectly handled via the scaffold stub rather than a dedicated create/update tool.