MCP Prompt Tool

You have a ready-to-use MCP server that automatically selects and generates specialized Claude Code prompts from a knowledge base of 66+ templates. It works in two modes: a local stdio server for seamless integration with your editor or IDE, and an HTTP server you can deploy for remote access. The server uses semantic search to find the best matching template and adapts it to your task, helping you accelerate prompt creation while keeping control over customization.

How to use

You connect your MCP client to the Prompt Template Selector server in one of two ways: the local stdio mode for tight editor integration, or the HTTP mode for a hosted endpoint. In stdio mode, you run the server alongside your editor, and commands are exchanged through standard input and output. In HTTP mode, you start a server that listens on a port and communicates over HTTP.

Once connected, you can list available templates, select the best-fitting template for your task, generate a ready-to-use prompt, and sync templates from the centralized collection. These actions enable you to browse, tailor, and apply prompt templates with minimal friction.

How to install

Prerequisites you need before installing: Bun v1.0+ and an Anthropic API key.

Step-by-step setup and run flow:

# Clone the repository
# Replace with your actual path if you clone to a different directory
# Note: Use your actual repository URL when cloning
# git clone https://github.com/YOUR_USERNAME/mcp-prompt-tool.git
# cd mcp-prompt-tool

# Install dependencies
bun install

# Configure API key ( Anthropic )
echo "ANTHROPIC_API_KEY=your-api-key-here" > .env

Configuration and operation notes

Environment variables you should configure include the Anthropic API key and the HTTP server port. The server uses these values at runtime to connect to the Claude Code API and to listen for HTTP requests.

For local development, you can run the server in stdio mode to enable editor integration, or start the HTTP server for remote access. The stdio and HTTP entrypoints are described in the connection steps and examples.

Security and deployment notes

Keep your API key secret and do not commit it to version control. Use environment management practices to inject credentials at runtime. When deploying HTTP, ensure you use proper access controls and consider placing the server behind a reverse proxy with TLS termination.

Available tools

list_templates

List and search available prompt templates by category or text query to understand what templates exist and can be used.

select_template

Find the best matching template for your described task using semantic search and optional context to tailor the template.

generate_prompt

Create a ready-to-use prompt by applying the selected template to your task, returning an actionable prompt ready for editing or execution.

sync_templates

Sync the local template index with the centralized GitHub repository to fetch new or updated templates.