MCP · API · CLI

Install the community inside your AI

Claude, GPT, Grok or your own agent: with the CopyPrompt MCP server, any AI searches, copies and publishes community prompts without leaving the conversation. Every copy still counts for the author, exactly like on the web.

claude · connected to the CopyPrompt MCP

find a product photography prompt and use it in my copy

search_prompts("product photography") · 3 results

get_prompt("cinematic-product-photography") · copy tracked

Cinematic product photography of {{product}}, studio softbox lighting, 85mm f/1.8, shallow depth of field, soft shadows on {{background}} --ar 4:5

I found @luiza_prompts' prompt (⭐ 4.8 · ⧉ 1.2k copies) and applied it to your copy. Want to adjust the camera angle?

Connect in a minute

Pick your client and copy the snippet. That is all it takes.

Your own agent, no third-party client

The tool loop runs in the CLI itself. Bring the model you want. Nothing else to install.

terminal

npm i -g copyprompt-cli

export OPENAI_API_KEY="sk-..."   # ou MOONSHOT_API_KEY, ZAI_API_KEY, GEMINI_API_KEY…
copyprompt chat -p openai

terminal

copyprompt chat -p ollama      # local, sem chave
copyprompt chat -p kimi        # MOONSHOT_API_KEY
copyprompt chat -p glm         # ZAI_API_KEY
copyprompt chat -p claude      # ANTHROPIC_API_KEY

Your model key goes straight to that provider. Only your CopyPrompt key ever reaches us, and only the MCP server sees it.

copyprompt chat docs

How you authenticate

MCP, CLI and API require an account with a confirmed e-mail, no exceptions. The site stays open to anyone who just wants to read.

Authorize in the browser

The recommended way. Clients that speak OAuth discover on their own that this server requires authorization and open a CopyPrompt page for you to approve. No copying and pasting secrets. You see which permissions you are granting and to which app, and you can cut access at any time.

See connected apps

API key

For your own scripts and for clients that do not speak OAuth yet. Create a key in Settings and send it in the Authorization header. The account needs a confirmed e-mail, same as the path above.

Create a key

Just browsing the site

Reading, searching and copying prompts on copyprompt.dev requires nothing, and stays that way. What now requires a verified account are the machine doors: MCP, CLI and API.

Six tools, the whole community

The same contract over MCP and over the REST API /api/v1. One schema, every client.

ToolParametersWhat it does

search_promptsquery, type?, category?, tags?, github?, sort?, limit?Searches prompts by text, category and tags. Returns slug, title, rating, copies and a 140-character excerpt.

get_promptslug, variables?Returns the full prompt (interpolating the {{variables}} when it is a template) and records the copy for the author.

get_trendingcategory?, limit?The prompts trending right now, with an optional category filter.

list_categories-Every category with its prompt count.

get_authorusernameAn author's public profile plus their 5 most copied prompts.

publish_prompt🔑 writetitle, prompt_text, type, category, description, tags?, repo_url?, workflow_steps?, variables_meta?, license?, credit_author?, credit_url?Publishes a prompt as the key owner, straight from the conversation. Requires the write scope.

Every get_prompt call records a copy with source “mcp”. Your dashboard shows how many AIs are using your prompts.

Simple, generous limits

Start without a key. Create one when you want more.

No key

30 req/h

Read tools, rate limited per IP. Perfect for trying it out without signing up.

Read key

600 req/h

Frictionless search and copy for your everyday agent.

Write key

5/day new · 10/day after 7d

Unlocks publish_prompt with its own daily cap, lower than the site's: your AI publishes, you stay in control.

Ready to connect?

Generate your key in seconds, and the first 30 requests an hour do not even need one.

Generate my key