MCP Prompt Templates Server

What is MCP Prompt Templates Server?

MCP Prompt Templates Server is a Model Context Protocol (MCP) server that provides the "prompts" primitive for managing and serving customizable prompt templates. It allows users to create, organize, and serve prompt templates for tasks like meeting analysis, content summarization, and blog post creation.

How to use MCP Prompt Templates Server?

Install with npm install, build with npm run build, and start with npm start. Configure an MCP client (e.g., Claude Desktop) by adding the server to its MCP settings JSON, pointing to the compiled dist/server.js or using tsx during development. Templates are loaded from the templates directory automatically.

Key features of MCP Prompt Templates Server

• Dynamic template loading from a templates directory
• YAML-based configuration for metadata and arguments
• Support for runtime argument substitution using Mustache syntax
• Type-safe implementation with TypeScript
• Implements the standard MCP prompts primitive

Use cases of MCP Prompt Templates Server

• Creating reusable meeting analysis prompts with dynamic fields
• Generating content summarization templates for blog posts
• Building structured weather forecast prompts with city and date arguments

FAQ from MCP Prompt Templates Server

How do I configure this server with an MCP client?

Add an entry to the client's MCP settings JSON with the command node and args pointing to the built dist/server.js, or use npx tsx with the source file during development.

What are the runtime dependencies?

Node.js and npm are required. During development, TypeScript and tsx are needed for hot-reloading.

How do I create a new prompt template?

Create a subdirectory inside templates/ with a descriptive name, containing a config.yaml file (for metadata and argument definitions) and a template.md file (for the prompt content with Mustache placeholders).

What argument syntax is used in templates?

Placeholders use double curly braces, e.g., {{ argument_name }}. Argument names must match the name field in config.yaml.

Can I use optional arguments?

Yes. In config.yaml, set required: false for an argument. The server will still substitute it if provided, but won't require it.