Short-form hook styles, script structures, retention and CTA rules for creators.
Short-form content mechanics for AI agents: hooks, script structures, retention, CTAs. The first 2 seconds decide the next 28.
Disclaimer. Structured content-mechanics frameworks from documented short-form practice. Platforms change; specificity and payoff don't.
AI agents drafting short-form content default to the same failure: greeting openers, hype adjectives, three ideas per video, and four CTAs. This MCP gives the agent the mechanics that survive contact with the feed — and auditors that fail drafts before they cost a post.
The house rule everything here enforces: receipts over hype. A number you can screenshot beats any adjective.
| Tool | What it returns |
|---|---|
get_hook_mechanics | 10 hook styles as fill-in structures with why each works + failure mode |
audit_hook | PASS/NEEDS WORK on a hook line: 2-second window, greetings, hype vs receipts, style detection |
get_script_structure | Beat-by-beat timing for talking_head, voiceover_broll, tutorial, storytime, ugc_ad |
audit_script | Full script audit: hook, spoken length, single-CTA law, zero-numbers check |
get_retention_mechanics | Open loops, payoff scheduling, pattern breaks, specificity ladders, loop endings |
get_cta_rules | CTA rules by goal (follow, comment seed, lead magnet, product, save/share) |
get_full_pack | Everything in one payload for agent context |
npx content-hooks-mcp # once published to npm
# or from source:
git clone https://github.com/closermethod/content-hooks-mcp && cd content-hooks-mcp && npm i && npm run build && node dist/main.js
Claude Desktop config:
{ "mcpServers": { "content-hooks": { "command": "npx", "args": ["content-hooks-mcp"] } } }
Get seen (this one) → get positioned (personal-brand-mcp) → get the reply (outbound-engine-mcp) → price the deal (creator-deals-mcp) → own the audience (newsletter-growth-mcp). Full catalog: MCP Hub
Elisabeth Hitz — 10+ years enterprise sales (Deel, Criteo, HBO), reverse-engineered for creators.
License: MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y content-hooks-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-closermethod-content-hooks-mcp": {
"command": "npx",
"args": [
"-y",
"content-hooks-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencecontent-hooks-mcpnpmio.github.closermethod/content-hooks-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.