A
licenseA
qualityA
maintenanceA Model Context Protocol server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations for effective workflow automation.
28
77,070 npm
22,906
MIT
Claude Prompts MCP Server
by minipuft
Related Servers
Alternatives to Claude Prompts MCP Server
- AlicenseAqualityCmaintenanceProvides structured spec-driven development workflow tools for AI-assisted software development with sequential spec creation (Requirements → Design → Tasks). Features a real-time web dashboard for monitoring project progress and managing development workflows.5376 npm4,293GPL 3.0
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI-native prompt management for Latitude.so with full CRUD operations, version control, file-based workflows, and direct prompt execution with streaming support.4 npm-
- AlicenseNot gradedqualityAmaintenanceEnables prompt versioning, evaluation, and management via MCP, CLI, and REST APIs, with support for multiple LLM providers.MIT
- AlicenseNot gradedqualityDmaintenanceEnables creation, management, and templating of prompts through a simplified SOLID architecture, allowing users to organize prompts by category and fill in templates at runtime.13 npm118MIT
- AlicenseAqualityCmaintenanceEnables storage and reuse of prompt templates with variable substitution for LLMs. Supports creating, searching, and retrieving prompt templates to avoid repeating complex instructions across conversations.46 npm4MIT
- FlicenseNot gradedqualityDmaintenanceProvides stateful prompt optimization using research-backed techniques like APE and OPRO, learning from historical performance data via a vector database. It enables users to automatically refine prompts, retrieve high-performing examples, and track performance analytics through iterative feedback.4-
- AlicenseAqualityAmaintenanceThe control plane for AI prompts that scores, enforces policy, locks config, and audits every prompt decision.206 npm2Elastic 2.0
TDQS
B3/5.0
Scored across 3 tools
Disambiguation4/5
The three tools target distinct areas: prompt execution, system administration, and resource management. The only ambiguity is system_control, whose description is vague and could overlap with engine control, but overall the boundaries are clear enough.
Naming Consistency4/5
All tool names use a consistent snake_case noun_noun format with a role suffix (engine, control, manager). While not a strict verb_noun pattern, the naming style is uniform and predictable across all three tools.
Tool Count4/5
Three tools is at the lower end of appropriate for a focused server, and each tool serves a distinct purpose. The count is reasonable for the narrow domain, though a slightly larger set could add more convenience functions.
Completeness4/5
The set covers the full lifecycle: creating and managing resources via resource_manager, executing prompts via prompt_engine, and system-level status via system_control. Minor gaps include a dedicated inspection or debugging tool, but the core workflows are complete.
Maintenance
ActivityActive
ResponsivenessSlow