Display.dev turns any HTML or Markdown file into a stable URL gated by your company's auth. Pick the path that matches how you work today – every path produces the same artifact, and you can switch between them.
From your terminal
The dsp CLI publishes a file in one command. Reach for it when you have a build pipeline, a script, or a one-off file on disk.
From your agent
MCP is the protocol Cursor, Codex, Claude Code, and other agents use to publish for you. Configure it once; the agent calls the publish tool when you ask.
From a browser
Use Web upload to publish an HTML or Markdown file. Use the browser extension to comment on the page currently open in Chrome, then publish its rendered state with or without those comments.
From your CI pipeline or app
GitHub Actions, GitLab CI, or any build server can publish on merge with dsp plus a DISPLAYDEV_API_KEY secret.
Next
If you've never published before, start with the Quickstart for one CLI publish from installation to a browser-ready URL. Concepts introduces the small vocabulary the rest of the docs assume; Plans & features is for evaluators comparing tiers.