# VersionPill > The visual side of your coding terminal. Product memory for builders who ship with coding agents. VersionPill is where product state lives while agents build in Grok, Claude, Cursor, or any MCP client: board, vision, versions, public changelog, roadmap, and a customer version badge ("the pill"). ## Core idea The terminal builds. VersionPill remembers the product. Not a Linear alternative. Not "PM with a chatbot." The visual half of the agent room. ## Who it's for - Coding agents (MCP tools + lean session context) - Founders / builders preparing work without chat novels - Team humans who share the same board as agents - Customers (pill + public ship page in user language only) ## Key pages - Home: https://versionpill.com/ - Sign up: https://versionpill.com/signup - Sign in: https://versionpill.com/signin - MCP endpoint (agents): https://mcp.versionpill.com/mcp - Connect (humans): https://versionpill.com/connect - Public changelog / roadmap / ideas: https://versionpill.com/ship/{workspace}/{project} ## Product surfaces - Board — issues agents and humans move (priority, type, labels, PRs) - Vision — what's building / shipped, kept warm next to the board - Ship — draft + publish customer-facing versions - Pill — embeddable badge of the last *published* version only - Public page — changelog, roadmap, ideas inbox (no eng ticket IDs) ## MCP Endpoint: https://mcp.versionpill.com/mcp **Connect (recommended):** paste URL only into Claude / Cursor → browser OAuth → Authorize once. No API key. **Advanced:** static Bearer key for scripts / hosts without OAuth (desk Settings → MCP connect → Advanced). Session pattern: get desk context → work with tools → log session delta. Never paste full product docs into chat. ## Positioning (do not confuse) - Not a Jira / Linear / Notion killer - Public surfaces use customer language only (no PREFIX-N, no eng jargon) - Versions publish when users should care — not on every commit ## Contact / brand - Site: https://versionpill.com - Product name: VersionPill - Short: vp