One prompt layer for Claude Code, Cursor, Codex, Gemini CLI, Antigravity, MCP clients, and any coding agent that can call an API. Turn rough requests into precise, project-aware task briefs with compact context and verification steps.
Each client gets the best available connection method: native hook where possible, MCP where supported, API where the tool can call HTTP, and copy-ready briefs when the tool has no integration surface yet.
Use it for: hands-free enhancement of every coding request. The companion CLI installs a UserPromptSubmit hook, collects safe repo context (branch, scripts, README, file hints), and injects a droPrompt brief before Claude starts — you keep typing naturally.
Use it for: IDE chats and Composer tasks. Add the droPrompt MCP server in Cursor settings and call its tools to enhance a task before Composer runs it. Pair with generated .cursorrules for project conventions.
Use it for: terminal agent sessions. Codex supports MCP servers in config.toml — register droPrompt once and ask Codex to enhance the task first. Or wrap it: fetch a brief from the API, then launch Codex with it.
Use it for: Gemini-driven coding sessions. Gemini CLI reads MCP servers from ~/.gemini/settings.json — add droPrompt there and its prompt tools appear natively. The brief endpoint also works as a pre-step.
Use it for: editor agents with an MCP surface. Where the build exposes MCP config, register droPrompt and enhance in-editor. Otherwise generate a copy-ready brief on this site and paste it into the agent.
Use it for: custom IDE extensions, internal dev tools, CI bots, and agents without an MCP surface. POST the rough task with bounded context, get back enhancedPrompt + injectedContext, hand it to any agent.
The first direct installer is Claude Code. Other tools use MCP, API, or copy workflows until their native automation surface is confirmed.
Install once, paste your droPrompt API key from Dashboard → Account → API Keys, then let the hook enhance each coding request.
mkdir -p ~/.local/bin
curl -fsSL https://droprompt.com/install/droprompt-claude.mjs \
-o ~/.local/bin/droprompt-claude
chmod +x ~/.local/bin/droprompt-claude
droprompt-claude login
droprompt-claude setup
droprompt-claude statusWhether the request comes from a hook, MCP tool, API call, or manual paste, droPrompt converts it into a compact engineering brief before the agent burns tokens on discovery.
The developer types naturally, even if the task is vague or missing project details.
The integration adds safe signals: project type, scripts, branch, README, rules, and file hints.
The API turns intent plus context into a clean implementation task with boundaries.
Claude Code, Cursor, Codex, Gemini, or another agent starts with enough context to avoid blind exploration.
The brief includes tests, checks, and risk notes so the output is easier to trust.
Every coding task type benefits differently. These are the patterns developers run through droPrompt every day — each one works over the hook, MCP, or the API.
Vague bug reports become bounded investigations: where to look, what not to touch, and which regression test to add.
One line becomes a spec: acceptance criteria, files likely involved, edge cases (encoding, large files), and a verification step.
The brief pins behavior-preservation as a hard constraint and demands tests pass before/after — so the agent refactors instead of rewriting.
Gets the agent to read the real test setup first (runner, fixtures, mocks) and target meaningful behaviors, not line coverage.
Turns a lazy ask into a structured review brief: correctness, security, performance lenses with severity-ranked findings.
Frames a hypothesis-driven investigation — what changed, what to measure, what evidence settles it — before the agent touches code.
Use API keys from the dashboard and send `X-API-Key` from CLIs, extensions, MCP servers, internal tools, or custom IDE automations.
POST /api/coding/briefPOST /api/coding/enhancePOST /api/claude-code/enhancePOST /api/generatePOST /api/refine / POST /api/enhanceGET /api/keys / POST /api/keysSend the rough task, target tool, and bounded project context. droPrompt returns `enhancedPrompt` and `injectedContext`.
curl -X POST https://droprompt.com/api/coding/brief \
-H "Content-Type: application/json" \
-H "X-API-Key: dp_..." \
-d '{
"client": "cursor",
"prompt": "fix checkout bug",
"context": {
"branch": "feature/payments",
"scripts": ["npm test"],
"hints": ["src/payment", "tests/payment"]
}
}'Claude Code direct hook is the first concrete installer. Cursor, Codex, Gemini CLI, Antigravity, and other tools are supported through the available surfaces listed here: MCP, API, generated rules, or copy-ready briefs. Native installers are added only when the tool exposes a reliable integration path.
API keys, coding brief API, Claude Code endpoint compatibility, manual/copy workflow, and MCP/API positioning.
Cursor rules/MCP documentation, Codex wrapper, Gemini CLI wrapper, and Antigravity workflow once native hooks are confirmed.
Bounded context by default: no `.env`, private keys, tokens, or full-source uploads unless a future team policy explicitly allows it.
Use droPrompt as the task-brief and context layer across Claude Code, Cursor, Codex, Gemini CLI, Antigravity, MCP tools, and your own developer automations.