One-command publishing
Send output from Claude Code, Cursor, Codex, or stdin and turn it into a live URL with one command.
jit
Revendiquerjit publishes AI-generated HTML, Markdown, files, and whole projects to a live URL from tools like Claude Code, Cursor, Codex, CLI, or stdin. It also offers MCP, REST API, drag-and-drop publishing, and a self-hosted option.
Overview
jit is a publishing layer for AI-native builders. It takes content produced by tools such as Claude Code, Cursor, Codex, or a CLI workflow and turns it into a live URL in one command.
The site says jit can publish HTML, Markdown, files, and entire projects. It is presented as open-source and MIT-licensed, with both a cloud beta and a self-hosted option for teams that want control over their data and deployment.
The product is positioned around fast handoff from AI generation to something shareable online, rather than around editing or content creation itself. That makes it useful when an agent, CLI command, or automated workflow has already produced the material and the next step is shipping it publicly.
Because the homepage emphasizes MCP, REST API, and drag-and-drop publishing, jit appears designed to fit both agent-driven and manual workflows without changing the destination format.
Features
Multi-format content handling
Publish HTML, Markdown, files, and entire projects rather than only a single post or asset.
MCP-native access
Use jit through MCP, plugins, or a REST API so different agents and tools can reach the same publishing layer.
Cloud or self-hosted deployment
Run jit in the cloud beta or self-host the whole stack if you want to control where content lives.
Versioned URLs
The site states that URLs are versioned, which suggests published outputs can be tracked over time.
Use cases
Ship agent output to a live URL
Use jit when an AI agent has finished generating a page, file set, or project and you want to publish it without manually rebuilding the handoff.
Publish from command-line workflows
Use the CLI or stdin path to turn terminal-generated content into something shareable as part of a scripted workflow.
Connect agent tools to one publisher
Use the MCP server or REST API when you want Claude, Cursor, or another agent tool to send output into the same publishing system.
Keep publishing infrastructure in-house
Use self-hosting when you need the publishing layer to run inside your own environment and keep control of the stack.
Pros and Cons
Pros
- Covers a clear workflow from AI-generated output to a live URL.
- Supports multiple input paths, including CLI, MCP, API, and drag-and-drop publishing.
- Can handle HTML, Markdown, files, and whole projects.
- Offers both cloud beta and self-hosted deployment.
- States that the project is open-source and MIT-licensed.
Cons
- The pricing page is unavailable on the provided site, so pricing and plan structure are not clear from the source.
- The evidence is mostly homepage-level, so feature depth and workflow limits are not fully documented in the supplied pages.
FAQ
Can I self-host jit?
jit is described as open-source and MIT-licensed, and the homepage says you can use the cloud beta or self-host the whole stack.
What inputs or workflows does jit support?
The homepage says jit can publish content from Claude Code, Cursor, Codex, or stdin, and also mentions an MCP server, REST API, and drag-and-drop publishing.
What kinds of content can jit publish?
The homepage describes jit as a publishing layer for AI-native builders that can publish HTML, Markdown, files, and entire projects.
How much does jit cost?
The source does not show a public pricing page; the pricing URL returns a 404 page, so pricing details are not available from the provided evidence.
Quick Facts
- Category
- Developer Tool
- Primary use
- Publishing AI-generated content
- Inputs
- Claude Code, Cursor, Codex, CLI, stdin
- Output
- Live URL
- Deployment
- Cloud beta or self-hosted
- License
- MIT