Taprun source ↗
Entry · devto

devto/post

Publish an article on Dev.to

modifies data (write)

Run it

$ tap devto/post

What it returns

ColumnType
statustext
urltext

Arguments

NameTypeDefaultDescription
titlestringArticle title
bodystringArticle body in Markdown
tagsstringComma-separated tags (up to 4)
publishedbooleanPublish immediately (default: true)

What it does

Publish an article on Dev.to

Install Taprun once

Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:

brew install LeonTing1010/tap/taprun
tap mcp connect

Or drop this into your claude_desktop_config.json (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):

{
  "mcpServers": {
    "tap": {
      "command": "tap",
      "args": ["mcp", "start"]
    }
  }
}

Call devto/post

Terminal, once installed:

tap run devto/post

From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:

tap.run({ site: "devto", name: "post" })

Why compile it once

This plan was forged once — the AI read devto, picked stable structural addresses (JSON-LD, ARIA, RSS, or declared API endpoints, in that priority order), and saved them to a .plan.json. Every replay since then has used zero LLM tokens. When devto ships a site change that breaks the extraction, tap verify surfaces it before your data goes stale — not after your pipeline silently writes garbage for a week.

Related devto taps

tapdescription
devto/publishPublish an article on Dev.to
devto/topDev.to top articles

Provenance

Source
LeonTing1010/tap-skills/blob/main/community/devto/post.plan.json
Machine format
post.jsonld — W3C Annotation
Last verify run
never
License
MIT