The Prompt Library You Can Plug Straight Into Claude Code

What do you need?

• Claude Code installed and working in your terminal.
• About 2 minutes for the install itself.
• Optional: a free API key from prompts.chat/settings, only needed if you want Claude to save or create prompts back to your own account rather than just search the public library.

How do you install it? (About two minutes.)

These are the exact commands from prompts.chat's own Claude Code plugin documentation. Run them inside a Claude Code session, not in a plain terminal.

/plugin marketplace add f/prompts.chat
/plugin install [email protected]

The first line points Claude Code at the prompts.chat marketplace. The second installs the plugin from it, which wires up the MCP connection, two slash commands and two agents in one step.

Add your own account (optional)

Skip this unless you want Claude to save or improve prompts back to your prompts.chat account, not just search the public library. Grab a key from prompts.chat/settings, then set it as an environment variable before you launch Claude Code:

export PROMPTS_API_KEY=your_api_key_here

If you're not on Claude Code

prompts.chat also exposes itself as a plain MCP server, for tools that don't support Claude Code's plugin marketplaces. Point any MCP-compatible client at the remote server, or run it locally if you'd rather not depend on their hosting:

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

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

How do you use it?

1. Restart or reopen Claude Code so the new plugin loads.
2. Search the library directly when you know roughly what you want:
   claude code

   Copy

   /prompts.chat:prompts cold outreach email
   /prompts.chat:prompts logo concept --type IMAGE
   /prompts.chat:prompts code review --category coding

3. Or describe the task in plain English and let Claude decide whether a library prompt fits. The plugin includes an auto-activating prompt-manager agent, so you don't have to remember the slash command exists. Try "find me a good prompt for writing a product launch tweet" in a normal message.
4. Search skills the same way, since the plugin covers both prompts and Claude skills:
   claude code

   Copy

   /prompts.chat:skills pdf

5. Point it at your own work. With PROMPTS_API_KEY set, ask Claude to save a prompt you liked, or improve one against a brief you give it, and it writes back to your prompts.chat account instead of just reading the public list.

What if it goes wrong?

What's the trap, and what won't this do?

The trap is treating the library as a shortcut around your own briefing. A library prompt still needs your context filled in. And ten thousand prompts sitting in a browser tab you don't open is worth less than twenty your agent can reach mid-task. Wiring the library in as MCP turns "I should look that up" into something Claude just does.

A prompt you have to go find is a prompt you'll stop using.

Sources and honesty notes: this guide is built from prompts.chat's own repository at github.com/f/prompts.chat, including its CLAUDE-PLUGIN.md file for the exact install and usage commands. The size of the library ("10,000 prompts") is a figure commonly quoted for this project and is stated here as a widely repeated claim, not a count I verified myself line by line. Commands and MCP config shown are current as of this write-up and may change between versions, so check the repository if something doesn't match.