Skip to main content
Glama
seungwonme

prompt-new-mcp

by seungwonme
README.md
# prompt-new-mcp

A Model Context Protocol (MCP) server for saving and managing prompts. This tool allows you to save prompts with timestamps and list previously saved prompts.

## Installation

You can run this MCP server directly using npx without installation:

```bash
npx prompt-new-mcp
```

## Usage with Claude Desktop

Add this server to your Claude Desktop configuration:

### macOS
Edit `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "prompt-new-mcp": {
      "command": "npx",
      "args": ["-y", "prompt-new-mcp"]
    }
  }
}
```

### Windows
Edit `%APPDATA%\Claude\claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "prompt-new-mcp": {
      "command": "npx",
      "args": ["-y", "prompt-new-mcp"]
    }
  }
}
```

## Available Tools

### save
Saves a prompt with a timestamp to the `prompts` directory.

**Parameters:**
- `name` (string): The name for the prompt file
- `content` (string): The prompt content to save

### list
Lists saved prompts in the prompts directory.

**Parameters:**
- `limit` (number, optional): Maximum number of prompts to return (default: 20)

## File Organization

Prompts are saved in the `prompts` directory with the following naming convention:
`YYYYMMDD_HHMMSS_<sanitized-name>.md`

Example: `20250125_143022_user-question.md`

## Requirements

- Node.js 18 or higher
- Compatible with Claude Desktop and other MCP clients

## License

MIT

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: 'list' retrieves existing prompts, while 'save' logs user messages. There is no overlap or ambiguity between these functions, making it easy for an agent to choose the correct tool based on the task.

Naming Consistency5/5

Both tool names follow a simple, consistent verb-only pattern ('list' and 'save'), which is clear and predictable. There are no deviations in naming style, making the set easy to understand at a glance.

Tool Count2/5

With only 2 tools, the server feels thin for a prompt management system. While 'list' and 'save' cover basic logging and retrieval, there are obvious gaps like updating, deleting, or searching prompts, which limits functionality for the domain.

Completeness2/5

The tool surface is severely incomplete for prompt management. It lacks essential operations such as update, delete, search, or get specific prompts, leaving agents unable to perform full CRUD workflows. The 'save' tool's mandatory use for logging also seems misaligned with typical prompt management tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues