Skip to main content
Glama
marcmodin

mcp-prompt-server

by marcmodin
README.md
<div align="center">

# 🚀 MCP Prompt Server

**A lightweight Model Context Protocol server for dynamic prompt management**

[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue.svg)](https://www.python.org/downloads/)
[![MCP](https://img.shields.io/badge/MCP-Compatible-green.svg)](https://modelcontextprotocol.io)
[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
[![Release](https://img.shields.io/github/v/release/marcmodin/mcp-prompt-server?sort=semver)](https://github.com/marcmodin/mcp-prompt-server/releases)

</div>

---

## ✨ Features

- 📁 **Dynamic Prompt Loading** — Automatically discover and register markdown files from the `prompts/` directory
- 📚 **Resource Management** — Serve documentation and reference materials via MCP resources
- ⚡ **Zero Configuration** — Add prompts and resources by simply creating markdown files with YAML frontmatter
- 🔒 **Security First** — Built-in path traversal protection, file size limits, and input validation
- 🎯 **MCP Compliant** — Full implementation of MCP prompt and resource primitives via FastMCP framework
- 🌐 **Remote Installation** — Run directly from GitHub without cloning

## 🔧 Requirements

- Python >=3.11
- Package manager: `uv` (installs automatically with `uvx`)

## Quick Start

### Using with Claude Cli

Add this configuration to your Claude Cli MCP settings:

```json
{
  "mcpServers": {
    "prompt-server": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/marcmodin/mcp-prompt-server@v0.1.0",
        "mcp-prompt-server"
      ]
    }
  }
}
```

### Using with GitHub Copilot

Create `.vscode/mcp.json` in your project:

```json
{
  "mcpServers": {
    "prompt-server": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/marcmodin/mcp-prompt-server@v0.1.0r",
        "mcp-prompt-server"
      ]
    }
  }
}
```


### Running Remotely

```bash
# Run directly from GitHub
uvx --from git+https://github.com/marcmodin/mcp-prompt-server@v0.1.0 mcp-prompt-server

# Debug with MCP Inspector
npx @modelcontextprotocol/inspector uvx --from git+https://github.com/marcmodin/mcp-prompt-server@v0.1.0 mcp-prompt-server
```

## 📚 Documentation

- **[Architecture](docs/architecture.md)** — System design and security model
- **[Contributing](docs/contributing.md)** — Development workflow and guidelines
- **[Prompt Template](resources/prompt-template.md)** — Creating prompt files

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The single 'ping' tool is unambiguous.

Naming Consistency5/5

Only one tool exists, so naming consistency is not an issue. The name 'ping' follows a common, clear convention.

Tool Count1/5

A single 'ping' tool is far too minimal for a server named 'mcp-prompt-server'. The server does not fulfill its implied purpose of providing prompt-related functionality.

Completeness1/5

The server completely lacks any prompt-related tools. A single ping-pong tool leaves a vast gap in functionality for a server that should handle prompts.

Maintenance

ActivityInactive
ResponsivenessNo issues