Prompts.Chat MCP Server

A MCP server for prompts.chat

Local serverstdio

What is the Prompts.Chat MCP server?

A MCP server for prompts.chat. That is what the prompts.chat mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Access thousands of AI prompts directly in your AI coding assistant

  • MCP Prompts — - Browse and use prompts directly via MCP prompts capability
  • Search Prompts — - Search for AI prompts by keyword, category, or tag
  • Get Prompt — - Retrieve prompt details by ID with variable substitution
  • Variable Support — - Prompts with ${variable} syntax are automatically handled

Getting it running

@fkadev/prompts.chat-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • search_prompts — Search for AI prompts by keyword. Supports filtering by type, category, and tag
  • get_prompt — Get a prompt by ID. Supports variable elicitation for prompts with template variables
  • save_prompt — Save a new prompt to your account. Requires PROMPTS_API_KEY.
  • Requirements — Add this to your Cursor MCP config file (~/.cursor/mcp.json):

What it needs from you

Configuration is passed through the environment: PROMPTS_API_KEY, PROMPTS_QUERY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js >= v18.0.0 - An MCP-compatible client (Cursor, Windsurf, VS Code, Claude Code, etc.) Install in Cursor Add this to your Cursor MCP config file (~/.cursor/mcp.json):

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Prompts.Chat's toolset — search_prompts, get_prompt, save_prompt and 1 more — is a fair guide to whether it matches your workflow. It is maintained by f; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
search_promptsSearch for AI prompts by keyword. Supports filtering by type, category, and tag.
get_promptGet a prompt by ID. Supports variable elicitation for prompts with template variables.
save_promptSave a new prompt to your account. **Requires PROMPTS_API_KEY.**
RequirementsAdd this to your Cursor MCP config file (~/.cursor/mcp.json):

How to install the Prompts.Chat MCP server

{
  "mcpServers": {
    "prompts-chat": {
      "url": "https://prompts.chat/api/mcp"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js >= v18.0.0 - An MCP-compatible client (Cursor, Windsurf, VS Code, Claude Code, etc.) Install in Cursor Add this to your Cursor MCP config file (~/.cursor/mcp.json):
VariableDescriptionRequired
PROMPTS_API_KEYCredential the server authenticates with.Yes
PROMPTS_QUERYConfiguration value read at startup.Optional

Example prompts to try

  • Use Prompts.Chat to search prompts.
  • Use Prompts.Chat to get prompt.
  • Use Prompts.Chat to save prompt.

Frequently asked questions

It connects Prompts.Chat to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (search_prompts, get_prompt, save_prompt, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Prompts.Chat directly.