Dead Drop Content
Turn a topic into a publish-ready, SEO-shaped article with optional stock images while you ship a blog or marketing site.
Overview
io.github.holmesclaw-hash/dead-drop-content is a MCP server for the Launch phase that generates SEO-oriented, publish-ready articles (with optional Unsplash images) from a topic via Ollama.
What is this MCP server?
- Send a topic and receive article copy tuned for SEO publishing
- Optional Unsplash image matching when UNSPLASH_ACCESS_KEY is set
- Runs via stdio npm package dead-drop-mcp (v0.1.1)
- Local LLM through OLLAMA_URL (default http://localhost:11434)
- Images are disabled automatically without an Unsplash key
- Server version 0.1.1
- Stdio transport via npm package identifier dead-drop-mcp
- Default Ollama endpoint http://localhost:11434
What problem does it solve?
Solo builders stall on long-form SEO content because drafting and image sourcing pull them out of their agent-first shipping workflow.
Who is it for?
Indie hackers running local Ollama who want agent-driven blog and SEO pages alongside product work.
Skip if: Teams that need governed brand voice, legal review workflows, or fully managed hosted content APIs without self-hosted LLM setup.
What do I get? / Deliverables
After you register the server, your agent can return structured article drafts (and images when configured) you can paste or commit as launch content.
- SEO-oriented article body from a supplied topic
- Optional matched Unsplash imagery when the API key is configured
Recommended MCP Servers
Journey fit
Output is optimized for search and publishing, which maps to the Launch phase when solo builders need pages and posts that rank and convert. Primary value is SEO-oriented long-form content, not distribution channels or app-store metadata.
How it compares
MCP content generator wired to local Ollama, not a hosted SEO SaaS or a generic writing skill with no image pipeline.
Common Questions / FAQ
Who is dead-drop-content for?
Solo and indie builders who publish content for distribution and SEO and already use Claude Code, Cursor, or similar MCP-capable agents.
When should I use dead-drop-content?
Use it during Launch when you need article drafts from a topic, especially before publishing blog posts, docs marketing pages, or changelog stories.
How do I add dead-drop-content to my agent?
Install the dead-drop-mcp npm package (v0.1.1), set OLLAMA_URL to your Ollama instance, optionally set UNSPLASH_ACCESS_KEY, and register the stdio MCP server in your agent MCP config.