GodPrompt MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| extensions | {
"io.modelcontextprotocol/skills": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_god_promptA | Returns the complete GodPrompt.md — a single-file universal system prompt for AI software development (63KB, ~1145 lines). Use this when you want the full payload in one shot. For progressive disclosure (smaller context), use get_core_skill and the reference tools instead. |
| get_core_skillA | Returns SKILL.md — the lean core protocol (~32KB) covering the universal 6-phase protocol, Three Iron Laws, and task auto-classification. Load it at the start of a task or after a context reset, then reuse that context instead of reloading it on every message. Start here for progressive disclosure. |
| get_protocolsA | Returns references/01-PROTOCOLS.md — deep execution guides for each task type (BUILD, DEBUG, REFACTOR, CONTENT, DESIGN, SHIP, ANALYZE, AUTOMATE, PLAN). Load this when the task requires detailed protocol steps beyond the core skill. ~13KB. |
| get_gatesA | Returns references/02-GATES.md — verification checklists, THE GATE (pre-completion verification), and structured report templates for every deliverable type. Load when you need to verify work before claiming completion. ~9KB. |
| get_anti_patternsA | Returns references/03-ANTI-PATTERNS.md — red flags, rationalizations, and recovery patterns. Covers the 10 most dangerous anti-patterns that lead to broken code, scope creep, and false confidence. Load when you catch yourself rationalizing. ~9KB. |
| classify_taskA | Classify one concrete software-development task into one of GodPrompt's 9 task types (BUILD, DEBUG, REFACTOR, CONTENT, DESIGN, SHIP, ANALYZE, AUTOMATE, PLAN), or UNCLASSIFIED when no reliable route is detected. Returns JSON with task_type, deterministic confidence, protocol, matched_signals, alternative_task_types, ambiguous, and recommendation; use it for routing before loading detailed workflow text. |
| get_versionA | Returns JSON with the GodPrompt content version, MCP server version, repository, bundled file sizes and purposes, and task-type/protocol catalog. Use it to verify which GodPrompt content/server version a client is connected to; use the content retrieval tools when you need the actual workflow text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| god-prompt | Production workflow skill for coding, debugging, architecture, design, deployment, automation, SEO, content, and other substantial build or review work. Use when a task benefits from explicit scope, task classification, evidence-backed execution, verification, and delivery gates. Routes work through the appropriate protocol and scales depth to the task while preserving user and developer authority. |
| references/01-PROTOCOLS.md | |
| references/02-GATES.md | |
| references/03-ANTI-PATTERNS.md |
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.