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
83,221 npm
23,166
MIT
Claude Prompts MCP Server
by minipuft
Related Servers
Alternatives to Claude Prompts MCP Server
- AlicenseAqualityFmaintenanceProvides 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.5333 npm4,303GPL 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 gradedqualityBmaintenanceEnables users to manage, search, render, version, and regression-test local Markdown templates with typed variables, and to expose them as MCP tools and native prompts without requiring a model API, account, or cloud service.MIT
- AlicenseNot gradedqualityAmaintenanceEnables prompt versioning, evaluation, and management via MCP, CLI, and REST APIs, with support for multiple LLM providers.MIT
- AlicenseAqualityBmaintenanceEnables refining prompt intent, structure, constraints, and output instructions before prompts reach an LLM, with tools for schema retrieval, brief validation, and prompt variant generation.3MIT
- AlicenseAqualityBmaintenanceEnables creation, management, and templating of prompts through a simplified SOLID architecture, allowing users to organize prompts by category and fill in templates at runtime.715 npm117MIT
- 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.414 npm4MIT
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