Glossary
The words PinDrop uses, defined.
A short reference for the terms you'll run into: pins, sessions, reviewers, MCP, and the rest. Plain definitions, no jargon for its own sake.
- Pin
- A single anchored comment placed on a page. PinDrop captures the route, viewport, pixel position, DOM selector, and a screenshot automatically, so the comment carries its own context.
- Anchored feedback
- Comments tied to an exact element and pixel position on a live page, instead of floating in a Slack thread. The feedback knows which page and which button it's about.
- Project
- One deployed app or site under review. You can swap its URL (staging today, prod tomorrow) without it counting as a new project.
- Session · share link
- The shareable URL you hand to reviewers. Sessions never expire. The link keeps working and the pins stay anchored.
- Reviewer
- Anyone leaving feedback. No account, no extension, no email required. They click the link and drop pins. That zero friction is why testers actually engage.
- Zero-signup reviewer
- A reviewer who leaves feedback without creating an account. The default in PinDrop, and the reason a shared link doesn't get ignored.
- Numbered pins
- Project-scoped pin numbers (pin 1, pin 2, …) shown in the UI. You say "fix pin 4" and your coding agent knows exactly which one. Better ergonomics than UUIDs.
- MCP (Model Context Protocol)
- An open protocol that lets coding agents (Claude Code, Cursor, Codex) call PinDrop tools: list open pins, read a pin's full context, comment, and resolve. Free on every tier, the Free plan included.
- Resolve
- Marking a pin as done after the fix ships. Agents can resolve pins over MCP, so the loop closes in the IDE.
- Workspace
- A team container holding multiple projects and members, available on the Studio tier.
- Embed script
- An optional one-line script tag. Paste a URL and PinDrop renders the page; the script is only needed for SPAs that need route-aware pinning.
Now try it on a page of your own.
no signup to share · free MCP with a free account