GodPrompt MCP Server
Related Servers
Alternatives to GodPrompt MCP Server
- AlicenseAqualityAmaintenanceAI visibility tracker MCP server. Track brand citations across ChatGPT, Claude, Perplexity, Gemini & Google AI Overviews. Self-host on Cloudflare Workers. GEO/AEO.122,009 npm39MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent development workflows, coordinating lead, explorer, consultant, builder, and reviewer roles through server-owned task claims, action logs, handoffs, and health-gated completion. Also provides read-only skills for use cases, specs, triage, consultation, test writing, reviews, and product documentation across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
- AlicenseAqualityDmaintenanceAutomatically generates and manages a prompts system for software projects, enabling persistent context for AI coding assistants through project scanning, requirement clarification, and module tracking.836 npmMIT
- 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
- FlicenseNot gradedqualityDmaintenanceProvides AI-powered selection and generation of specialized system prompts from a database of over 66 templates for Claude Code. It uses semantic search to find the best matching template and can adapt it to fit specific user tasks and contexts.-
- AlicenseNot gradedqualityAmaintenanceEnables decomposing raw prompts into structured, typed blocks and recompiling them into Claude-optimized machine-readable XML prompts, all callable directly from Claude Code conversations. Also exposes the full set of available block types and their recommended canonical ordering for manual crafting.MIT
- AlicenseAqualityDmaintenanceProvides specialist context for AI agents, enabling them to work as different roles (UI, DE, SRE, etc.) through MCP prompts and tools.716 npm1MIT
TDQS
Scored across 7 tools
Each tool targets a clearly distinct artifact or operation: full prompt, core skill, anti-patterns, gates, protocols, task classification, and version metadata. The only apparent overlap—get_god_prompt versus progressive-disclosure tools—is explicitly distinguished by payload size and intended use.
All names use a consistent verb_noun snake_case convention: get_god_prompt, get_core_skill, get_anti_patterns, get_gates, get_protocols, get_version, and classify_task. The classify_task deviation is still a clear verb_noun pattern and matches its operation.
Seven tools are well scoped for a progressive-disclosure prompt-content server. Each tool earns its place by covering a distinct file or routing/metadata function without overwhelming the caller.
The surface covers the full payload, lean core skill, all referenced operational documents, task classification, and version/catalog metadata. An agent can start lean, route tasks, load detailed guidance, verify work, and recover from anti-patterns without obvious dead ends.