Ext Ops Panel
Open dashboard
Comparison

Repo To Content vs ArtifactSmith

Repo To Content is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ArtifactSmith is an MCP server published by vrijsinghani. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceRepo To ContentArtifactSmith
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 1.1.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Forks (GitHub): 2
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Repo To Content vs ArtifactSmith
FactRepo To ContentArtifactSmith
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)2 (better)
Last release (differs)2026-10-24 (better)2026-10-17 (worse)
Where it runs (differs)Installs as a plugin bundleRemote server (artifactsmith.neuralami.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/danielrosehill/claude-repo-to-content-plugingithub.com/vrijsinghani/artifactsmith
Changes in the last 7 days (differs)10
First seen (differs)2026-10-152026-10-17
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Repo To Content

In its own words, on Community GitHub marketplaces:

Convert GitHub repos into polished content (PDF, white paper, internal doc, public-docs publication) via Typst, with optional AI banner generation and multi-target publishing.

ArtifactSmith

In its own words, on Official MCP Registry:

Turns agent output into versioned web pages, PDFs, Word docs, spreadsheets and Markdown.

How to run each

Repo To Content As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install repo-to-content@danielrosehill

ArtifactSmith As a remote MCP server

Claude Code
claude mcp add --transport http artifactsmith https://artifactsmith.neuralami.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ArtifactSmith has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Repo To Content · What it can do: ArtifactSmith · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built