Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

For scoped engineering tasks, use classify_task to route the work and get_tailored_guidance to load only the needed phase. Use get_core_skill if the entire core protocol is needed, not on every request. Use review_code_change, audit_requirements and build_test_matrix for bounded caller-supplied evidence and draft test planning. Use diagnose_failure, assess_release_readiness, create_context_handoff and compare_evaluation_runs only for their respective supplied-evidence workflows. Use audit_agent_trajectory, trace_change_impact, review_mcp_tool_contracts, audit_agent_instructions and design_adversarial_tests only with explicit caller-supplied bounded inputs; they produce unverified review hints or test ideas. None of these tools run external checks, authenticate evidence, authorize release or independently verify work. Load get_protocols, get_gates, or get_anti_patterns only when focused guidance is insufficient. Use get_god_prompt only when the full single-file payload is preferable; request bounded start/maxChars chunks if an MCP bridge truncates large responses. All GodPrompt tools are read-only. For coding tasks with scoped changes or required proof of completion, use classify_task then create_work_contract to define explicit acceptance, scope and actual verification commands before implementation. After authorized work, provide redacted command receipts and changed paths to review_work_evidence. All evidence is caller-supplied; a review is not independent verification, approval, or completion authorization.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}
extensions
{
  "io.modelcontextprotocol/skills": {}
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_god_promptA

Returns the complete GodPrompt.md — a single-file universal system prompt for AI software development (63KB, ~1145 lines). With no arguments, returns the original full text for backward compatibility. Bridges may truncate the middle of such a large response: pass start (initially 0) and maxChars (at most 8192) to retrieve bounded, lossless chunks; structuredContent.nextStart gives the next offset, or null at EOF. For progressive disclosure, use get_core_skill and references 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.

create_work_contractA

Create a portable, SHA-256-fingerprinted task contract with explicitly provided scope, acceptance criteria, verification commands and prohibitions. Deterministic, read-only and stateless. Use classify_task first; missing details produce NEEDS_DEFINITION, never inferred commands or permission to execute.

review_work_evidenceA

Fail-closed audit of a create_work_contract result against supplied changed paths, command receipts, criteria, prohibited actions and risk review. Returns HOLD or REPORTED_READY_FOR_INDEPENDENT_REVIEW; never independently verifies caller-supplied evidence or authorizes completion, merge or deployment.

review_code_changeA

Analyze a bounded unified diff for line-anchored risk signals, changed-file coverage, and review follow-ups. Heuristics only: not a semantic review, vulnerability scanner or verified test result. Stateless, no repository access.

audit_requirementsA

Inspect bounded requirement text for missing acceptance scenarios, qualitative obligations and duplicates. Returns source-line-linked clarification prompts; cannot validate business correctness.

build_test_matrixB

Draft bounded positive, negative, boundary and regression test cases for supplied requirements. Reuses the requirements parser, reports unspecified expectations and never claims tests ran.

get_tailored_guidanceB

Return only the relevant task-type protocol or quality gate for one phase, paged into small bounded chunks. More efficient than loading the entire reference; no tool execution or verification.

diagnose_failureA

Return bounded evidence-class hypotheses and differentiating experiments for supplied symptoms/logs. Does not expose raw logs or claim a root cause.

assess_release_readinessA

Check caller-reported CI checks, source/artifact revision, rollback, migration and approvals for missing blockers; never authorize deployment or authenticate receipts.

create_context_handoffB

Compose a bounded, explicitly unverified state transfer from caller-reported decisions, open items and evidence references, with best-effort token/email redaction.

compare_evaluation_runsA

Compare bounded caller-reported outcomes on exact matching case IDs, with coverage exclusions and low-sample warnings. No API calls, statistical significance claims or stored results.

audit_agent_trajectoryA

Read-only review of bounded, sanitized event metadata for repeated failures, scope drift, stale verification and premature completion. No raw logs or independent execution evidence; cannot authorize an agent.

trace_change_impactA

Rank affected files and select test cases with explicit dependency and requirement-to-test mappings. All graph and receipt evidence must be supplied by caller; no repository or command execution.

review_mcp_tool_contractsA

Read-only bounded design audit of MCP tool descriptions, input/output schemas and annotations. Not a protocol validator, vulnerability scanner or permission grant.

audit_agent_instructionsA

Review bounded caller-supplied instruction documents for duplicates, possible opposing action constraints and risky bypass wording. No instruction is executed or promoted.

design_adversarial_testsA

Generate bounded negative, boundary, metamorphic, property and trust-boundary test ideas from explicit caller-supplied field contracts. Never runs or generates executable tests.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
godprompt-evidence-viewRead-only interactive display of caller-supplied engineering findings and affected dependencies.
god-promptProduction 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

A3.7/5.0

Scored across 22 tools

Disambiguation4/5

Most tools target a distinct artifact and action (classify_task, review_code_change, create_work_contract), but progressive-disclosure retrieval tools such as get_tailored_guidance versus get_protocols/get_gates overlap in purpose. The two test-generation tools, build_test_matrix and design_adversarial_tests, also have adjacent boundaries, though descriptions mostly resolve the distinction.

Naming Consistency5/5

All names use consistent snake_case action_object phrasing, with clear verb families such as get_, review_, audit_, create_, and build_. There is no mixed casing or vague one-word naming.

Tool Count3/5

At 22 tools, the server sits in the heavy 16-25 range and requires agents to scan a large surface before choosing. Each tool appears to earn a place in a broad GodPrompt workflow suite, but the count is borderline for easy navigation.

Completeness4/5

The surface covers content retrieval, task classification, contract creation, multiple audit/review dimensions, test ideation, release readiness, handoff, and evidence review. Remaining gaps, such as no execution/verification, no persistence, and no semantic review, appear to be intentional scope limits rather than accidental dead ends.

Maintenance

ActivityActive
ResponsivenessNo recent community issues