Artifacts for Cursor

Cursor's agent writes the file into your repo, which is right for code and wrong for the thing you wanted to show someone. A rendered report or a prototype page has no business being committed just so a colleague can look at it. With thing configured, the agent publishes it instead and hands back a link, and your repo stays code.

Connect thing to Cursor

Cursor reads MCP servers from .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project. Add thing:

{
  "mcpServers": {
    "thing": {
      "command": "npx",
      "args": ["-y", "@unravel-tech/thing", "mcp"],
      "env": { "THING_TOKEN": "paste-your-token-here" }
    }
  }
}

Committing the project level file shares the setup with everyone on the repo, so keep the token out of it and let each person run thing login once instead.

What Cursor can do once it is connected

Ask it to publish and it calls push_artifact with an HTML page, a Markdown doc, an image, or a PDF, then reports the URL. Push the same name again and you get a new immutable version at the same address, with /diff/1/2 showing what changed between any two. Readers leave comments on the page itself, anchored where the question is. Visibility runs from one named person through team, anyone with the link, and fully public.

The other two tools are list_artifacts, for what you have already published, and whoami, for which account and team it is pushing to.

Not using Cursor for everything?

The same artifacts work from every other agent, and from CI. See artifacts for any coding agent for Claude Code, Aider, Cline, shell tools, and pipelines, and for why a page that outlives the session it came from is worth the extra step of publishing.