display.dev for Devin
Devin builds it. display.dev is where your engineering team reviews it. Configure the display.dev MCP server and Devin can publish its HTML outputs directly to a company-gated URL – without human intervention.
Devin produces outputs. Sharing them requires the same broken workflow.
Devin (by Cognition) is an autonomous AI software engineer. It writes code, creates documentation, generates HTML reports – and leaves outputs on disk or in a repository.
When Devin produces an HTML artifact, the sharing problem is the same regardless of which agent generated it:
- GitHub Pages – requires Enterprise Cloud for private repos. Non-engineers don't have GitHub accounts.
- Manual deploy – someone still has to run a deploy command. Defeats the point of autonomous generation.
- Screenshot – kills the interactivity Devin built.
- Public URL – no company auth on internal outputs.
The right solution: Devin publishes its HTML output autonomously, using an MCP tool, as part of the task.
Agent-native publishing with MCP
display.dev's MCP server gives Devin a publish tool. Add it to Devin's tool configuration:
{
"mcpServers": {
"display-dev": {
"url": "https://mcp.display.dev",
"apiKey": "your-api-key"
}
}
}Now instruct Devin to publish as part of a task:
"Generate an architecture proposal for the auth migration and publish it to the team."
Devin generates the HTML, invokes the publish tool, and returns the company-gated URL in the task summary. No manual publish step. No one needs to be at a terminal.
Or: CLI in the CI step
If Devin's workflow involves a CI pipeline, add display.dev as a publish step:
- name: Publish Devin output
run: dsp publish ./devin-output/ --name "task-${{ env.TASK_ID }}"
env:
DISPLAY_TOKEN: ${{ secrets.DISPLAY_TOKEN }}Every Devin task that produces HTML output generates a permanent authenticated URL automatically.
Agentic artifact sharing compared
| Option | Autonomous publish | Company auth | Viewer friction | Cost |
|---|---|---|---|---|
| GitHub Pages | ✅ (with Actions) | ❌ / $2,100/mo | High (GitHub account) | $0 / $2,100/mo |
| Vercel deploy + SSO | ✅ (with Actions) | ✅ | Medium | $320+/mo |
| Manual screenshot | ❌ | – | Low (degraded) | $0 |
| display.dev (MCP) | ✅ | ✅ | Zero | $49/mo flat |
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 90 days audit logs
For compliance-driven organizations.
From $499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 365 days audit logs
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays a living document, not a one-shot screenshot.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Claude Code, Codex, and Cursor all work, along with anything else that creates HTML or Markdown output. The best agent changes. The home doesn't: your URLs, versions, and comments stay put when you switch.
Common questions.
Does display.dev work as an MCP tool for any agent, not just Devin?
Yes. display.dev's MCP server exposes publish, find, get, and delete tools. Any MCP-compatible agent – Devin, Claude Code, Cursor, custom agents – can use them.
What types of HTML artifacts does Devin typically produce?
Devin generates architecture documents, implementation plans, code documentation, test reports, and analysis outputs – often as HTML files. display.dev publishes all of them.
Can Devin publish multiple artifacts per task?
Yes. Each publish call creates a new artifact. Devin can publish interim artifacts (e.g., a plan before implementation starts) and final artifacts (the completed output).
How do viewers authenticate if they're in different departments?
Any @yourcompany.com email authenticates – engineering, product, executive, legal. No separate accounts or access provisioning required.
What if Devin produces a multi-file directory?
publish supports directory publishing. The entire output directory is served as a single artifact, with index.html at the root.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).