Skip to main content
Glama
minipuft

Claude Prompts MCP Server

by minipuft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_PROMPTS_PATHNoPath to your custom prompts directory only
MCP_RESOURCES_PATHNoPath to your custom resources directory (can contain: prompts/, gates/, methodologies/, styles/)

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
prompt_engineA

🚀 PROMPT ENGINE [CAGEERF]: Execute prompts with C.A.G.E.E.R.F framework and ground-truth validation.

WHAT IT RETURNS: Prepared prompt + CAGEERF phase instructions (Context→Analysis→Goals→Execution→Evaluation→Refinement). WHAT YOU DO: Execute each phase yourself using the returned structure.

SYNTAX:

  • prompt_id key:"value" # Run prompt with arguments

  • step1 --> >>step2 # Chain multiple steps

  • @CAGEERF >>prompt # Apply CAGEERF framework

  • :: verify:"npm test" :full # Shell validation (5 attempts, 5min)

  • :: verify:"cmd" loop:true # Autonomous until pass

PRESETS: :fast (1 try), :full (5 tries), :extended (10 tries) MODIFIERS: %clean (no injection), %lean (gates only), %judge (preview)

system_controlD

⚙️ SYSTEM CONTROL [CAGEERF]: System administration. Status shows current CAGEERF phase context.

resource_managerB

🗂️ RESOURCE MANAGER [CAGEERF]: Unified CRUD for prompts, gates, and frameworks.

USAGE: resource_manager(resource_type:"prompt|gate|framework", action:"...", ...) RESOURCE TYPES: prompt (templates), gate (quality criteria), framework (CAGEERF, ReACT, 5W1H, SCAMPER) ACTIONS: create | update | delete | list | inspect | reload | switch (framework only)

Use action:"guide" with resource_type:"prompt" for phase-appropriate recommendations.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

Resources