Content
# MCP Prompt Server
> 🚀 **Important Upgrade Notice!**
We are excited to announce a significant upgrade to our MCP Prompt Server, introducing a new service: [mypromptmcp.com](https://mypromptmcp.com/).
Through this platform, you can freely manage your prompts online and flexibly combine and package them into MCP services, easily integrating them into various AI Agents or tools (such as Cursor, Windsurf, Cline, etc.), achieving cross-platform invocation and efficient collaboration.
Experience more powerful prompt management and distribution capabilities now by visiting [mypromptmcp.com](https://mypromptmcp.com/) for more details!
> ⚠️ **Important Reminder:**
>
> MCP Prompt Server will continue to be available, but we will no longer perform functional upgrades and maintenance. If you wish to continuously obtain the latest features and experiences, we recommend migrating and using [mypromptmcp.com](https://mypromptmcp.com).
[English Version](README_EN.md)
This is a server based on Model Context Protocol (MCP) that provides preset prompt templates according to user task needs, helping Cline/Cursor/Windsurf... to execute various tasks more efficiently. The server returns preset prompts as tools to be better used in editors like Cursor and Windsurf.
## Features
- Provides preset prompt templates for tasks such as code review, API documentation generation, code refactoring, etc.
- Offers all prompt templates as MCP tools, not in MCP prompts format
- Supports dynamic parameter replacement for more flexible prompt templates
- Allows developers to freely add and modify prompt templates
- Provides a tool API for reloading prompts and querying available prompts
- Optimized specifically for editors like Cursor and Windsurf for better integration experience
## Directory Structure
```
prompt-server/
├── package.json # Project dependencies and scripts
├── src/ # Source code directory
│ ├── index.js # Server entry file
│ └── prompts/ # Preset prompt templates directory
│ ├── code_review.yaml
│ ├── api_documentation.yaml
│ ├── code_refactoring.yaml
│ ├── test_case_generator.yaml
│ └── project_architecture.yaml
└── README.md # Project documentation
```
## Installation and Usage
1. Install dependencies:
```bash
cd prompt-server
npm install
```
2. Start the server:
```bash
npm start
```
The server will run on standard input/output and can be connected by Cursor, Windsurf, or other MCP clients.
## Adding New Prompt Templates
You can create new prompt templates by adding new YAML or JSON files in the `src/prompts` directory. Each template file should contain:
```yaml
name: prompt_name # Unique identifier for calling this prompt
description: prompt description # Description of the prompt function
arguments: # Parameter list (optional)
- name: arg_name # Parameter name
description: arg description # Parameter description
required: true/false # Whether it's required
messages: # Prompt message list
- role: user/assistant # Message role
content:
type: text # Content type
text: | # Text content, can include parameter placeholders {{arg_name}}
Your prompt text here...
```
After adding a new file, the server will automatically load it at the next startup, or you can use the `reload_prompts` tool to reload all prompts.
## Usage Examples
### Calling Code Review Tool in Cursor or Windsurf
```json
{
"name": "code_review",
"arguments": {
"language": "javascript",
"code": "function add(a, b) { return a + b; }"
}
}
```
### Calling API Documentation Generation Tool in Cursor or Windsurf
```json
{
"name": "api_documentation",
"arguments": {
"language": "python",
"code": "def process_data(data, options=None):\n # Process data\n return result",
"format": "markdown"
}
}
```
## Tool API
The server provides the following management tools:
- `reload_prompts`: Reload all preset prompts
- `get_prompt_names`: Get all available prompt names
Additionally, all prompt templates defined in the `src/prompts` directory are provided as tools to clients.
## Integration with Editors
### Cursor
In Cursor, you need to edit the MCP configuration file:
1. Find or create Cursor's MCP configuration file (usually located in `~/.cursor/` directory)
2. Add the following content:
```json
{
"servers": [
{
"name": "Prompt Server",
"command": ["node", "/path/to/prompt-server/src/index.js"],
"transport": "stdio",
"initialization_options": {}
}
]
}
```
Make sure to replace `/path/to/prompt-server` with your actual project path.
3. Save the configuration and restart the editor
4. You should now see all available prompt tools in the tool panel
### Windsurf
In Windsurf, access MCP configuration by:
1. Navigating to Windsurf - Settings > Advanced Settings, or
2. Using the command panel > Open Windsurf settings page
3. Scroll to the Cascade section, you'll see the option to add a new server
4. Click "Add Server" button, then select "Add Custom Server+"
5. Alternatively, you can directly edit `~/.codeium/windsurf/mcp_config.json` file, adding:
```json
{
"mcpServers": {
"prompt-server": {
"command": "node",
"args": [
"/path/to/prompt-server/src/index.js"
],
"transport": "stdio"
}
}
}
```
Make sure to replace `/path/to/prompt-server` with your actual project path.
6. After adding the server, click the refresh button
7. You should now see all available prompt tools in the tool panel
## Extension Suggestions
1. Add more professional domain-specific prompt templates
2. Implement prompt version control
3. Add prompt categorization and tags
4. Implement prompt usage statistics and analysis
5. Add user feedback mechanism
