Skip to main content
Glama
Sign In
prompts.chat MCP Server

prompts.chat MCP Server

by f
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Features

  • 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

Related MCP server: Prompt Bookmarks

🛠️ Installation

Requirements

  • Node.js >= v18.0.0

  • An MCP-compatible client (Cursor, Windsurf, VS Code, Claude Code, etc.)

Add this to your Cursor MCP config file (~/.cursor/mcp.json):

Remote Server (Recommended)

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

Local Server

{
  "mcpServers": {
    "prompts-chat": {
      "command": "npx",
      "args": ["-y", "@fkadev/prompts.chat-mcp"]
    }
  }
}

Add this to your Windsurf MCP config file:

Remote Server (Recommended)

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

Local Server

{
  "mcpServers": {
    "prompts-chat": {
      "command": "npx",
      "args": ["-y", "@fkadev/prompts.chat-mcp"]
    }
  }
}

Add this to your VS Code MCP settings:

Remote Server (Recommended)

"mcp": {
  "servers": {
    "prompts-chat": {
      "type": "http",
      "url": "https://prompts.chat/api/mcp"
    }
  }
}

Local Server

"mcp": {
  "servers": {
    "prompts-chat": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@fkadev/prompts.chat-mcp"]
    }
  }
}

Remote Server (Recommended)

claude mcp add --transport http prompts-chat https://prompts.chat/api/mcp

Local Server

claude mcp add prompts-chat -- npx -y @fkadev/prompts.chat-mcp

Add this to your Zed settings.json:

{
  "context_servers": {
    "prompts-chat": {
      "command": {
        "path": "npx",
        "args": ["-y", "@fkadev/prompts.chat-mcp"]
      }
    }
  }
}

⚙️ Configuration

The local server supports the following environment variables:

Variable

Description

PROMPTS_API_KEY

Optional API key for authenticated requests

PROMPTS_QUERY

Optional query string to filter prompts (e.g., users=a,b&categories=c,d&tags=e,f)

Example with Environment Variables

{
  "mcpServers": {
    "prompts-chat": {
      "command": "npx",
      "args": ["-y", "@fkadev/prompts.chat-mcp"],
      "env": {
        "PROMPTS_API_KEY": "your-api-key",
        "PROMPTS_QUERY": "users=username&categories=coding&tags=productivity"
      }
    }
  }
}

🔨 Available Tools

Tool

Description

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.

📚 MCP Prompts

This server exposes all public prompts from prompts.chat as MCP prompts. Use prompts/list to browse available prompts and prompts/get to retrieve them with variable substitution.

📖 Example Usage

Ask your AI assistant:

Search for prompts about code review
Get the prompt for "act as a linux terminal"

🔗 Links

📄 License

ISC

Available Tools

2 tools
get_promptGet PromptB

Get a prompt by ID. If the prompt contains template variables (like ${variable} or ${variable:default}), you may need to provide values for them.

Inputs: id (required).

search_promptsSearch PromptsC

Search for AI prompts by keyword. Returns matching prompts with title, description, content, author, category, and tags.

Inputs: query (required), limit, type, category, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_prompt retrieves a specific prompt by ID with potential variable handling, while search_prompts finds multiple prompts by keyword with metadata. There is no overlap or ambiguity between these operations.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (get_prompt, search_prompts) with clear, descriptive names that align with their functions. The naming style is uniform and predictable.

    Tool Count3/5

    With only two tools, the server feels thin for a prompt management domain. While get and search are fundamental, typical CRUD operations like create, update, or delete prompts are missing, making the set feel incomplete for full prompt lifecycle management.

    Completeness2/5

    The toolset is severely incomplete for prompt management. It lacks essential operations such as creating, updating, or deleting prompts, which are core to managing a prompt repository. Agents will hit dead ends when trying to modify or add prompts.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches