prompts-mcp

masaki39/prompts-mcp

3.2

If you are the rightful owner of prompts-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.

The model context protocol server transforms Markdown files into callable MCP tools, allowing for custom prompts.

prompts-mcp

NPM Downloads

Simple MCP server that turns Markdown files into MCP tools or prompts (slash commands).

Prompt format

Each Markdown file is parsed once at startup. The file path becomes the tool/prompt name:

  • Root level: file.mdfile
  • Nested: project/feature.mdproject/feature

YAML frontmatter controls metadata:

---
description: Produce a concise project brief.
enabled: true
---
Prompt body goes here...
  • description – optional tool/prompt description (defaults to "Prompt defined in …")
  • enabled – defaults to true; set to false to disable

MCP config examples

As tools

{
  "mcpServers": {
    "prompts-mcp": {
      "command": "npx",
      "args": ["-y", "@masaki39/prompts-mcp@latest"],
      "env": {
        "PROMPTS_DIR": "/absolute/path/to/prompts"
      }
    }
  }
}

As prompts (slash commands)

{
  "mcpServers": {
    "prompts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@masaki39/prompts-mcp@latest",
        "--register-as=prompt"
      ],
      "env": {
        "PROMPTS_DIR": "/absolute/path/to/prompts"
      }
    }
  }
}

As both tools and prompts

{
  "mcpServers": {
    "prompts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@masaki39/prompts-mcp@latest",
        "--register-as=both"
      ],
      "env": {
        "PROMPTS_DIR": "/absolute/path/to/prompts"
      }
    }
  }
}

Examples

File structure:

prompts/
├── brief.md           → brief
├── review.md          → review
└── project/
    ├── init.md        → project/init
    └── deploy.md      → project/deploy

Using as MCP tool/prompts :

/brief
/review
/project/init
/project/deploy