vibe-prompt-mcp
Related Servers
Alternatives to vibe-prompt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceContext-aware prompt intelligence for Claude CLI that scores prompts against the real codebase and rewrites them with AI-enhanced context.1MIT
- FlicenseAqualityCmaintenanceRefines and improves AI prompts using workspace-aware context from your project's tech stack, structure, and dependencies. Includes tools to analyze prompt quality and generate well-structured prompts from raw ideas.4209 npm5-
- AlicenseNot gradedqualityCmaintenanceContext intelligence for AI coding sessions. 7 MCP tools to score, compare, compress, build, and scan prompts across 9 AI tools. Rule-based, <5ms/prompt, all analysis runs locally.46MIT
- AlicenseNot gradedqualityAmaintenanceStatic analysis for vibe-coded apps. Flags security, reliability, performance, and AI quality issues in code generated by Cursor, v0, Bolt, and Copilot.575 npm15MIT
- AlicenseAqualityAmaintenanceAI development observability platform. It silently captures structured data from vibe coding sessions via MCP and codifies deviation patterns into project rules to make AI write better code. 100% local and zero runtime dependencies.102 npm8MIT
- AlicenseNot gradedqualityAmaintenanceA code ingestion tool that transforms your code into AI-optimized prompts instantly. Gather the relevant context with code2prompt under the hood. Learn more at code2prompt.dev7,653MIT
TDQS
Scored across 2 tools
The two tools, score_prompt and optimize_prompt, suggest distinct actions, though the lack of descriptions leaves some room for overlap. An agent could generally tell them apart by verb alone.
Both tool names follow the same lowercase snake_case verb_noun pattern: score_prompt and optimize_prompt. The naming is fully consistent.
With only two tools, the server feels minimal and near the thin end of the acceptable range. It could be sufficient for a narrowly scoped prompt-tuning server, but the purpose is unclear without descriptions.
The surface covers scoring and optimizing prompts but lacks obvious supporting operations such as generation, comparison, or iteration. The missing descriptions also make it hard to confirm that the intended workflow is fully covered.