Hypertxt MCP Content Operations for Openclaw

Hypertxt is a controlled content-operations skill for inspecting, generating, reviewing, and publishing articles through the Hypertxt MCP server.

julianengel
v1.0.0
Jul 28, 2026
0
483
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install hypertxt

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install hypertxt using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Hypertxt MCP Content Operations?

Hypertxt gives AI agents a governed workflow for working with articles, editorial states, and Google Search Console data without guessing IDs or skipping approvals. It is designed as a controlled content-operations layer, prioritizing discovery and inspection before any generation, state changes, GSC refreshes, or publishing actions.

With Openclaw Skills, this workflow helps teams move from search opportunity discovery to article creation and publishing while maintaining strict permission boundaries. It supports article credits, workflow and project discovery, content export, editorial review, and connected destination publishing, all while requiring explicit user approval for irreversible actions.

Hypertxt MCP Content Operations Use Cases

  • Inspect remaining article credits before planning content production
  • Discover Hypertxt projects, workflows, articles, templates, and integrations
  • Find SEO opportunities in Google Search Console and turn them into article briefs
  • Generate an article only after confirming the exact project, template, title, keyword, and cost
  • Review article content, summarize editorial issues, and change state with approval
  • Export existing content for downstream review or reuse
  • Publish to a connected CMS as a draft or live article with explicit approval
  • Track article IDs, destination URLs, and state transitions across the content lifecycle

How Hypertxt MCP Content Operations Works

  1. Verify the Hypertxt MCP server exposes the required discovery tools, then confirm the client is configured with HYPERTXT_API_KEY in environment or secret storage.
  2. Start with read-only inspection: call account_status to check credits, list_projects to identify the target project, and related list tools to discover valid IDs.
  3. If content opportunity research is needed, use list_gsc_connections and query_gsc to inspect search performance data, then rank opportunities using clicks, impressions, CTR, and position.
  4. Present a concrete proposal that includes the project, template or workflow, title, primary keyword, audience, search intent, and brief before any generation step.
  5. Request explicit user approval before each write action: generate_article, change_article_state, sync_gsc, or publish_article.
  6. After generation, monitor article status with get_article or list_articles instead of regenerating while queued.
  7. For review, inspect the full article, summarize editorial concerns, and only then request approval to change state.
  8. For publishing, confirm the destination and mode first, then publish once approved and report the final URL and resulting state when available.

Hypertxt MCP Content Operations Setup

  1. Ensure your client can connect to the Hypertxt MCP server and exposes the discovery tools required by the skill.
  2. Store the API key securely as HYPERTXT_API_KEY in environment variables or the client secret manager. Never paste it into prompts.
  3. If the required MCP tools are missing, stop and follow the Hypertxt Openclaw guide rather than inventing configuration.
  4. Confirm the server supports at least account_status and list_projects before attempting any workflow.
  5. Use discovery tools first; do not guess project IDs, article template IDs, workflow IDs, GSC connection IDs, or publishing destination IDs.
export HYPERTXT_API_KEY="your-secret-key"
# Example: verify your client environment is set before connecting
printenv HYPERTXT_API_KEY

Hypertxt MCP Content Operations Data Schema & Taxonomy

Hypertxt organizes content operations around a small set of identifiable entities and stateful actions. Openclaw Skills should treat these as canonical objects and never infer IDs.

Entity Purpose Notes
Account Tracks article credits and account status Read via account_status before generation
Project Top-level content workspace Discover via list_projects
Workflow Editorial or generation path for a project Discover via list_workflows
Article Core content object Inspect via list_articles and get_article
Article Template Generation structure or format Must be selected explicitly; never guessed
GSC Connection Linked Search Console source Discover via list_gsc_connections
GSC Query Snapshot Search opportunity data Returned by query_gsc with optional date filters
Integration / Destination CMS or external publishing target Discover via list_integrations
Editorial State Lifecycle status such as reviewed, approved, ready, posted, published Updated only with approval

Generated or returned metadata typically includes:

  • Project ID and article ID
  • Article state before and after change
  • Credit count before generation
  • GSC window and filters used for queries
  • External destination URL after publishing
  • Action log indicating what was performed and what was intentionally not performed

State mapping rules:

  • reviewed and approved map to ready
  • posted maps to published as a manual state record
  • Destination drafts remain ready in Hypertxt and do not imply public publication

Hypertxt MCP Content Operations Advanced Features

  • Strict read-only vs write-action permission boundaries to prevent accidental state changes
  • Explicit approval gating for generation, editorial changes, GSC refreshes, and publishing
  • Google Search Console opportunity discovery with ranking based on clicks, impressions, CTR, and position
  • Controlled article generation that consumes exactly one credit per run
  • Destination-aware publishing with support for draft or live mode
  • Manual editorial state mapping that preserves operational clarity across systems
  • Safe failure handling for insufficient credits and HTTP 402 generation responses
  • Workflow discipline that requires discovery first, making Openclaw Skills safer for agentic content operations

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*