MCP Prompt

The MCP Prompt node allows you to create pre-configured prompt templates that users can easily invoke from their MCP client. These templates can include variable placeholders that users fill in, making it simple to create consistent, well-structured prompts for common tasks. Unlike tools and resources, prompts don't require flows or response nodes - they simply register the template with the MCP server.

Flow Requirements

None — MCP Prompt nodes do not require flows or MCP Response nodes. They only register the prompt template with the MCP server, making it available for users to select and customize in their MCP client.

Configuration

Name

string — Optional Optional display name for this node in the flow. This helps identify the node in your Node-RED editor but is not visible to MCP clients.

Server

mcp-server — Required The MCP server configuration this prompt will be registered with. Select from your configured MCP server instances.

Prompt ID

string — Required Unique identifier for the prompt used by MCP clients to access this prompt template. Use snake_case for naming.

Examples:

holiday_planner
code_reviewer
bug_report_template
meeting_summarizer

Title

string — Required Human-readable name shown to users in MCP clients. This is what users see when browsing available prompts.

Description

string — Required Detailed description of what this prompt does and when to use it.

Prompt Template

string — Required

Define your prompt text using double curly braces {{ }} for variables.

Arguments

JSON — Required JSON schema defining the template variables that users can customize. This follows the same JSON Schema format used in MCP Tool input schemas.

Prompt Template Examples

Basic Example

Hello ! Welcome to .

Variables: name, location

Complex Example

You are a holiday planning agent.
You should provide information about .
You should also provide rough budget ideas for visiting this place in  for  days.
Please break down rough ideas for hotels and local tourist hot spots to visit.

Variables: location, time_of_year, duration

Multi-Section Example

# Code Review Request

## File: 
## Language: 

Please review the following code:



Focus on:
- 
- 
- 

Provide feedback on code quality, potential bugs, and suggestions for improvement.

Variables: filename, language, code, focus_area_1, focus_area_2, focus_area_3

Argument Schema Examples

Basic Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Your name",
      "minLength": 1
    },
    "location": {
      "type": "string",
      "description": "The place you're visiting",
      "minLength": 1
    }
  },
  "required": ["name", "location"]
}

Extended Schema

{
  "type": "object",
  "properties": {
    "location": {
      "type": "string",
      "description": "A country, city or town somewhere in the world",
      "minLength": 1
    },
    "time_of_year": {
      "type": "string",
      "description": "A specific date, season or month giving context for the travel period",
      "minLength": 1
    },
    "duration": {
      "type": "number",
      "default": 7,
      "description": "The number of days for the trip"
    }
  },
  "required": ["location", "time_of_year"]
}

Schema with Enums and Defaults

{
  "type": "object",
  "properties": {
    "report_type": {
      "type": "string",
      "description": "Type of report to generate",
      "enum": ["daily", "weekly", "monthly", "quarterly"],
      "default": "weekly"
    },
    "include_charts": {
      "type": "boolean",
      "description": "Include visual charts in the report",
      "default": true
    },
    "detail_level": {
      "type": "string",
      "description": "Level of detail for the report",
      "enum": ["summary", "detailed", "comprehensive"],
      "default": "detailed"
    }
  },
  "required": ["report_type"]
}