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.

Already connected? Publish your first artifact

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.

Publish your first artifact

Paste this into Cursor. It creates a real artifact; no existing file is required.

Your first-publish prompt

Use thing’s whoami tool to confirm my account and team. Create a small self-contained HTML report, let me review it, then call push_artifact with inline content, filename first-thing.html, and name first-thing. Omit visibility to use the workspace default. Return the URL and its visibility.

The agent should return a thing URL. Open it while signed in and confirm the report is there. Check Share before sending it. Personal artifacts open for anyone with the link; to keep a report restricted, push it to a team, where artifacts default to team-only and you can invite people one by one.

For your next report, use the same name to add a version at the same URL.

Something not working?

Check npx --version, then run npx -y @unravel-tech/thing@latest whoami on the machine running your agent. If sign-in is missing, run npx -y @unravel-tech/thing@latest login there and restart the agent. For MCP, confirm thing’s tools appear before asking it to publish. Never put credentials in a prompt or a committed config.

Try the direct terminal command or upgrade an older CLI.

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.

Check your published artifacts Choose another setup