Getprompts
Search getprompts.org’s catalog of battle-tested prompts from inside Claude Code or Cursor instead of copying from the browser.
Overview
getprompts is a MCP server for the Build phase that searches 1,000+ battle-tested prompts from getprompts.org inside your coding agent.
What is this MCP server?
- Searches 1,000+ battle-tested prompts sourced from getprompts.org
- Stdio npm package getprompts-mcp v0.1.0 for Claude Code, Cursor, and ChatGPT-class workflows
- Brings curated prompt patterns into the agent instead of ad-hoc prompt guessing
- Repository subfolder mcp-server under spark-prompts on GitHub
- Website getprompts.org linked from the official server manifest
- Catalog advertises 1,000+ battle-tested AI prompts
- Server version 0.1.0, npm identifier getprompts-mcp
- Website https://getprompts.org per server manifest
What problem does it solve?
Solo builders repeat weak generic prompts because searching a prompt site in the browser does not fit their Claude Code or Cursor loop.
Who is it for?
Indie developers who lean on agents daily and want a fast, cataloged prompt search without maintaining their own database first.
Skip if: Teams with strict prompt governance that forbid external prompt sources, or builders not using MCP in their editor.
What do I get? / Deliverables
After you add the MCP server, your agent can fetch relevant getprompts.org entries inline while you build and iterate automations.
- In-session search across 1,000+ cataloged prompts
- Faster agent instructions for coding and product tasks
- Stdio MCP setup reusable across projects
Recommended MCP Servers
Journey fit
Prompt libraries sit in Build under agent-tooling because they improve how your coding agent behaves while you ship features. getprompts wires external prompt discovery into the same session where you edit skills, rules, and automation.
How it compares
Remote prompt catalog search via MCP, not a skill pack, not prompt versioning, and not local prompt engineering tutorials.
Common Questions / FAQ
Who is getprompts for?
Solo builders using Claude Code, Cursor, or MCP-connected ChatGPT workflows who want searchable access to getprompts.org’s prompt library.
When should I use getprompts?
Use it during build and agent-tooling when you need proven prompt patterns for coding, debugging, content, or planning without leaving the IDE.
How do I add getprompts to my agent?
Install the getprompts-mcp npm package, add a stdio MCP server block in your client config, restart the editor, then call the search tools against getprompts.org.