Skip to main content
Glama
Prompt Refiner MCP Server

Prompt Refiner MCP Server

by nmelo

Prompt Refiner MCP Server

A Model Context Protocol server that helps systematically refine vague ideas into well-structured prompts through guided clarification.

Philosophy

This server follows the Sequential Thinking pattern:

  • Server provides STRUCTURE - tracks refinement steps, formats output, applies templates

  • Claude provides INTELLIGENCE - analyzes ideas, asks questions, decides when complete

  • Single focused tool with clear workflow

  • Visual progress feedback via colored stderr output

Related MCP server: PromptArchitect MCP

Installation

npm install
npm run build

Usage

Run Locally

node dist/index.js

Add to Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "promptrefiner": {
      "command": "node",
      "args": ["/Users/nmelo/Desktop/Projects/prompter/dist/index.js"]
    }
  }
}

Docker (Optional)

docker build -t promptrefiner .
docker run -i promptrefiner

How It Works

The Tool: promptrefiner

Three modes:

  1. Start - Begin refinement with original idea

    { originalIdea: "I want to build an API" }
  2. Clarify - Add clarifications for specific aspects

    {
      aspect: "purpose",
      clarification: "REST API for user authentication with JWT tokens"
    }
  3. Export - Generate refined prompt using a template

    {
      exportTemplate: "technical-spec",
      refinementComplete: true
    }

Aspects to Clarify

  • purpose (critical) - What is this for? What problem does it solve?

  • audience (critical) - Who will use this? Skill level?

  • constraints (important) - Requirements, limitations, technical constraints

  • context (important) - Where/when/how will this be used?

  • success (important) - How is success measured? What does "done" look like?

  • scope (helpful) - What's in/out of scope?

  • style (optional) - Tone, format, style preferences

Templates

  1. detailed-structured - Comprehensive with sections (Purpose, Audience, Requirements, etc.)

  2. concise-bullets - Brief bullet-point format

  3. technical-spec - Formal specification style

  4. conversational - Natural language paragraph

  5. minimal - Just the essentials

Example Session

User: Help me refine this idea: "I want to build an API"

Claude: [calls promptrefiner with originalIdea]

šŸŽÆ Starting Refinement
ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│ Original Idea                          │
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│ I want to build an API                 │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

Claude: Let me ask some clarifying questions:
- What will the API do? What's its main purpose?
- Who will use this API?
- Are there any technical requirements?

User: It's for user authentication. Developers will integrate it.
      Needs JWT tokens and should handle 1000 requests/sec.

Claude: [calls promptrefiner with aspect="purpose", clarification="..."]

šŸ” Step 2: Clarifying Purpose
ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│ REST API for user authentication      │
│ using JWT tokens                       │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

Step 2/5 | Covered: 1 aspect

[... more clarifications ...]

Claude: [calls promptrefiner with exportTemplate="technical-spec", refinementComplete=true]

✨ Step 5: Exported as technical-spec
ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│ Template: technical-spec               │
│ Aspects covered: 3                     │
│ Total steps: 5                         │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

Claude: Here's your refined prompt:

# Specification

**Purpose**: User authentication API using JWT tokens, handling login,
logout, and token refresh

**Target Users**: Developers integrating authentication into their applications

**Technical Requirements**: Handle 1000 requests per second, JWT token-based
authentication

**Deployment Context**: Not specified

**Acceptance Criteria**: Functional implementation

Features

āœ… Structured workflow - Systematic refinement process āœ… Multiple clarifications - Can clarify same aspect multiple times (concatenated) āœ… Visual progress - Colored console output with progress tracking āœ… Flexible templates - 5 built-in export formats āœ… Type-safe - Full TypeScript with strict validation āœ… oneOf schema - Enforces correct tool usage modes

Environment Variables

  • DISABLE_PROGRESS_LOGGING=true - Disable colored stderr output

Architecture

  • 346 lines of TypeScript

  • Single tool with oneOf validation

  • 5 template functions using template literals

  • State tracking via refinement history array

  • Duplicate handling - Multiple clarifications per aspect concatenated with \n\n

Development

npm run watch      # Watch mode during development
npm run build      # Build for production

License

MIT

Available Tools

1 tool
promptrefinerA

A tool for systematically refining vague ideas into well-structured prompts.

This tool helps you work with users to transform rough ideas into clear, actionable prompts through a structured clarification process.

Workflow:

  1. START: Submit the user's original idea

  2. CLARIFY: Ask the user questions and submit clarifications for key aspects:

    • purpose: What is this for? What problem does it solve?

    • audience: Who will use this? What's their skill level?

    • constraints: What are the requirements, limitations, or technical constraints?

    • context: Where/when/how will this be used? What environment?

    • success: How will success be measured? What does "done" look like?

    • scope: What's included? What's explicitly out of scope?

    • style: What tone, format, or style is needed?

  3. EXPORT: When refinement is complete, export using a template

Key aspects to explore (ask about these):

  • purpose (critical)

  • audience (critical)

  • constraints (important)

  • context (important)

  • success (important)

  • scope (helpful)

  • style (optional)

You decide what questions to ask based on what's unclear in the idea. You decide when enough clarification has been gathered. The tool just tracks your refinement steps and formats the output.

Available export templates:

  • "detailed-structured": Comprehensive with sections (Purpose, Audience, Requirements, etc.)

  • "concise-bullets": Brief bullet-point format

  • "technical-spec": Formal specification style

  • "conversational": Natural language paragraph

  • "minimal": Just the essentials

Inputs: aspect, originalIdea, clarification, exportTemplate, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.

    Naming Consistency5/5

    The single tool name 'promptrefiner' is clear and descriptive. While it doesn't follow a verb_noun pattern, consistency is trivially maintained with only one tool.

    Tool Count3/5

    The server has exactly one tool, which feels thin. However, the tool's purpose is narrowly scoped (prompt refinement), and the single tool encapsulates a complete workflow, making the count borderline but not extreme.

    Completeness4/5

    The tool covers the full prompt refinement lifecycle: start, clarify, and export with multiple templates. It appears functionally complete for its domain, though additional utilities (e.g., listing previous refinements) could be imagined.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      C
      maintenance
      Refines 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.
      4
      209 npm
      5
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Refines and optimizes prompts for LLMs through adaptive questioning and intelligent clarification workflows. Supports multiple AI providers (Google, OpenAI, Anthropic, Groq, Qwen) with interactive prompt enhancement and targeted modifications.
      18 PyPI
      17
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables users to enhance rough prompts into more detailed, clear, and effective versions using multiple AI providers like Anthropic, OpenAI, and Gemini. Supports custom templates and integrates with any MCP-compatible client.
      1
      66 npm
      Apache 2.0