@houtini/contentmarketingideas
OfficialProvides tools to query Search Console data including growing/declining queries, opportunities, and daily summaries to inform content strategy.
Enables monitoring subreddits as content sources for editorial brief generation.
Enables monitoring RSS feeds as content sources for editorial brief generation.
Allows publishing articles directly to WordPress via REST API, with credentials encrypted at rest.
Enables monitoring YouTube channels as content sources and pulling full transcripts for indexing into the RAG corpus.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@houtini/contentmarketingideas Show me this week's editorial briefs."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@houtini/contentmarketingideas
The MCP server for Content Marketing Ideas — the editorial copilot I built because I was tired of the same content research loop. You read a lot, you notice patterns, you get ideas, you write. The reading and pattern-spotting is the slow part, and most of it is mechanical.
This server pulls all of it into Claude Desktop, Claude Code, Cursor, or any MCP client: source monitoring, editorial briefs, voice-matched article drafts, RAG corpus search, Google Search Console data, and WordPress publishing. Around 70 tools, one npx command.
I wrote a long post about why the product exists and how I use it every day: Content Marketing Ideas — what it is, how I built it, and why I use it.
Quick Navigation
Get started | What it does | Tools reference | Configuration | Requirements
Get started in two minutes
Step 1: Get an account and an API key
Sign up at contentmarketingideas.co. Free tier covers five sources and weekly delivery, which is enough to wire the MCP up and try every tool. Once you're in, go to Dashboard → Account → API & MCP Server and click Generate API Key. The full key is shown once — copy it now. Keys are prefixed cr_.
Step 2: Add to your Claude Desktop config
Config file locations:
Windows:
C:\Users\{username}\AppData\Roaming\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"contentmarketingideas": {
"command": "npx",
"args": ["-y", "@houtini/contentmarketingideas"],
"env": {
"CMI_API_KEY": "cr_your_api_key_here"
}
}
}
}Step 3: Restart Claude Desktop
Tools show up automatically. npx pulls the package on first run — no separate install needed.
Claude Code (CLI)
Claude Code uses claude mcp add rather than the desktop config file:
claude mcp add -e CMI_API_KEY=cr_your_api_key_here -s user contentmarketingideas -- npx -y @houtini/contentmarketingideasVerify with claude mcp get contentmarketingideas — you should see Status: Connected.
Cursor / Windsurf / VS Code
Same shape, different config file. Add this block:
{
"contentmarketingideas": {
"command": "npx",
"args": ["-y", "@houtini/contentmarketingideas"],
"env": {
"CMI_API_KEY": "cr_your_api_key_here"
}
}
}Local build instead
For development, or if you'd rather not rely on npx:
git clone https://github.com/houtini-ai/contentmarketingideas-mcp
cd contentmarketingideas-mcp
npm install
npm run buildThen point your config at the local build:
{
"mcpServers": {
"contentmarketingideas": {
"command": "node",
"args": ["C:/path/to/contentmarketingideas-mcp/dist/index.js"],
"env": {
"CMI_API_KEY": "cr_your_api_key_here"
}
}
}
}Related MCP server: Fourth Brain Demo
What it does
Content Marketing Ideas isn't a "here's what's trending" feed. It's an editorial copilot — every brief is framed as "here's what you should write and why" rather than a data dump. The MCP exposes the same engine to Claude.
Editorial briefs from your sources
Use contentmarketingideas:list_briefs to show me this week's briefs for site-ae01a256The product watches RSS feeds, YouTube channels, subreddits, podcasts, and news keywords for you. When something relevant lands, four signal generators (trending, decay, untapped, gap) write briefs containing a thesis, editorial play, gap analysis, suggested format, what to cover, internal link suggestions, and two alternative angles (obvious / bold / contrarian). Each brief is enriched with keyword volume, difficulty, monthly trend, People Also Ask questions, competitive landscape, entity relationships from Wikidata, and an originality score versus existing coverage.
get_brief returns the full payload — synthesis, signal sources, enrichment, momentum sparkline, the lot. brief_feedback lets you train the system from inside Claude (thumbs_up / thumbs_down / made_this / already_covered). Thumbs-down auto-archives briefs you don't want to see again.
Voice-matched article generation
Use contentmarketingideas:create_article with source_type="brief" and source_id="<brief_id>"The web app analyses your published content with sixteen statistical analysers and produces a deterministic ~17KB writing-style guide. Article generation feeds that guide into Claude Sonnet so the output reads like you wrote it — not like an LLM. 1,300–1,800 words, full markdown, with Schema.org provenance and entity-tagged facts traceable back to the source.
generate_article queues an article for the production pipeline, regenerate_article re-runs failed jobs, get_article_provenance returns the source chain and Schema.org JSON-LD, and publish_article pushes the finished post straight to WordPress over the REST API (credentials encrypted at rest).
Topic Explorer — coverage as a map, not a list
Use contentmarketingideas:get_coverage_explore for site-ae01a256Topics are the unit of value. The Topic Explorer assembles every entity from your last 100 briefs plus your site's core topics, then enriches each with corpus matches, GSC traffic and 28-day sparklines, search volume, competitive landscape, parent/sibling topics from Wikidata, and a lifecycle state: covered, trending, gap, declining, or emerging. get_coverage_explore returns the full clustered dataset so you can ask Claude things like "which trending topics do I have zero coverage on?" or "cluster my declining pages by parent topic and suggest refreshes."
Search Console integration
Use contentmarketingideas:gsc_growing_queries with site_id="..." and limit=20GSC OAuth is per-site. Once connected, daily data feeds into brief generation and is queryable through the MCP: gsc_summary, gsc_queries, gsc_opportunities (high-impression, low-position), gsc_growing_queries, gsc_declining_queries, gsc_growing_pages, gsc_declining_pages, gsc_daily_summary for sparklines.
RAG corpus — your own knowledge base inside Claude
Use contentmarketingideas:search_rag with q="long-tail audience research methods" and limit=10The corpus is human-curated by design — your own published content, the sources you follow, and URLs you add manually. No auto-crawling junk. Documents are indexed into Cloudflare Vectorize (bge-m3, 1024d) and a D1 FTS5 index for hybrid semantic + keyword search. Long structured documents get section-aware embeddings with parent_id linkage, and queries dedupe sections back to their parent doc with a small breadth bonus.
populate_corpus indexes a list of URLs, populate_site walks a sitemap, populate_youtube pulls full transcripts from a YouTube channel. list_corpus_documents, delete_corpus_document, rag_stats, and search_rag round it out. Site-scoped — sources for site A don't pollinate site B's briefs.
Source management
Use contentmarketingideas:detect_source with url="https://example.com/feed"detect_source auto-identifies feed type (RSS, YouTube, Reddit, podcast, news) and resolves the canonical feed URL. add_source, update_source, delete_source, list_sources, get_source cover the rest. Sources are site-scoped, so a multi-site account never cross-contaminates briefs.
Pipeline triggers
Use contentmarketingideas:trigger_synthesis to generate briefs nowDon't want to wait for the cron run? trigger_ingestion runs all your sources, trigger_synthesis generates briefs from current content, trigger_profile re-runs site profile analysis (voice guide, topics, audience, content gaps). Useful for testing and for end-of-day "what came in today" runs.
Account, sites, deliveries, WordPress
Multi-site accounts are first-class. list_sites / create_site / update_site / delete_site / update_site_schedule for site management; list_account_emails / add_account_email / delete_account_email for multi-recipient delivery (Business+); get_wordpress_status / save_wordpress_credentials / delete_wordpress_credentials for publishing; list_deliveries for the email delivery audit trail.
Tools reference
Around 70 tools across seven groups.
Briefs
Tool | Description |
| List editorial briefs with filters (site, status, signal type, search) |
| Full brief detail: synthesis, enrichment, keywords, signals, momentum |
| Submit feedback ( |
| Delete a brief |
| Generate a voice-matched draft from a brief |
| Get the generated draft text |
Sources
Tool | Description |
| List content sources, optionally filtered by site |
| Source details and item count |
| Add RSS, YouTube, Reddit, podcast, or news source |
| Rename or set keyword filters / tags |
| Remove a source |
| Auto-detect source type from URL |
Articles
Tool | Description |
| List articles for a site |
| Full article with markdown, outline, research |
| Create from a brief, growth item, or custom prompt |
| Edit title, markdown, keywords, notes |
| Delete an article |
| Queue an article for AI generation |
| Re-run a failed or completed article |
| Publish to WordPress |
| Check WordPress publish status |
| Source attribution + Schema.org JSON-LD |
RAG corpus
Tool | Description |
| List indexed documents |
| Remove a document |
| Hybrid semantic + keyword search |
| Corpus statistics |
| Index URLs into the corpus |
| Index a site via sitemap |
| Index YouTube channel transcripts |
| Brief-vs-corpus coverage report |
| Topic Explorer data with clusters |
Growth & GSC
Tool | Description |
| Get the cached growth plan for a site |
| Generate a fresh growth plan |
| Trigger a Search Console sync |
| 28-day performance summary |
| Top queries with metrics |
| High-impression, low-position queries |
| Daily metrics for sparklines |
| Queries gaining performance |
| Queries losing performance |
| Pages gaining performance |
| Pages losing performance |
WordPress
Tool | Description |
| Check connection status |
| Connect WordPress (encrypted at rest) |
| Disconnect WordPress |
Account, sites, pipeline
Tool | Description |
| Account details, plan, usage, limits |
| Your sites with source/brief counts |
| Add a new site |
| Update site name / URL |
| Remove a site (cascades sources, briefs) |
| Set delivery frequency and hour |
| Delivery email recipients |
| Add an email recipient |
| Remove an email recipient |
| Site voice profile |
| Generate / refresh site profile |
| Run source ingestion now |
| Generate briefs from current content |
| Email delivery history |
Configuration reference
Variable | Required | Default | Description |
| Yes | — | Your API key from Dashboard → Account → API & MCP Server (starts with |
| No |
| API base URL — override only for self-hosted or staging |
Security
Your API key authenticates as your account and your account only. Every request is server-side authenticated against users.api_key (hashed). The API enforces ownership checks on every resource: you cannot read, modify, or delete another user's data even by guessing IDs. No X-User-ID impersonation header exists.
If a key leaks, revoke it from Dashboard → Account → API & MCP Server and generate a new one — old keys are immediately rejected.
Plans and limits
The MCP itself is free and open source. The platform behind it has tiered limits:
Plan | Sources | Sites | Frequency | Articles / month |
Free | 5 | 1 | Weekly | 0 |
Pro | 25 | 1 | Daily | 10 |
Business | 50 | 5 | Daily | 25 |
Publisher | 100 | 10 | Daily | 50 |
Free is enough to wire up the MCP and try every tool against real data. Pro unlocks daily delivery, voice-matched drafts, growth plans, and keyword analytics. Business adds multi-site, WordPress publishing, and competitor intel. Pricing is at contentmarketingideas.co/pricing.
Requirements
Node.js 18+
A Content Marketing Ideas account (free tier works) and an API key
An MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, or any other MCP host
Links
Product: contentmarketingideas.co
Why I built it: houtini.com — Content Marketing Ideas: what it is, how I built it, and why I use it every day
MCP spec: modelcontextprotocol.io
Licence
MIT
Available Tools
59 toolsadd_account_emailB
Add a delivery email recipient
Inputs: email (required).
add_sourceA
Add a content source (RSS feed, YouTube channel, Reddit subreddit, podcast, or news keyword)
Inputs: url (required), name (required), type (required), site_id.
brief_feedbackB
Submit feedback on a brief (thumbs_up, thumbs_down, made_this, already_covered)
Inputs: action (required), brief_id (required).
create_articleB
Create a new article. Can be from a brief (source_type=brief, source_id=brief_id) or custom.
Inputs: title (required), site_id (required), source_id, source_type, +4 more.
create_siteB
Create a new site (subject to plan limits)
Inputs: url (required).
delete_account_emailA
Remove a delivery email recipient (cannot remove primary)
Inputs: email_id (required).
delete_articleA
Permanently delete an article
Inputs: article_id (required).
delete_briefA
Permanently delete a brief and its feedback
Inputs: brief_id (required).
delete_corpus_documentB
Delete a single corpus document by ID
Inputs: doc_id (required).
delete_siteA
Delete a site (sources reassigned, briefs deleted). Cannot delete last site.
Inputs: site_id (required).
delete_sourceA
Remove a content source and its content items
Inputs: source_id (required).
delete_wordpress_credentialsB
Disconnect WordPress from a site
Inputs: site_id (required).
detect_sourceB
Auto-detect source type and feed URL from a URL
Inputs: url (required).
generate_articleB
Queue article for AI generation (research, outline, draft, voice check). Returns immediately.
Inputs: article_id (required).
generate_draftA
Generate a voice-matched draft article for a brief (uses site profile voice guide)
Inputs: brief_id (required).
generate_growth_planA
Generate a new growth plan for a site (syncs GSC, runs analysis)
Inputs: site_id (required).
get_accountA
Get your account details: plan, usage, limits, sites
Inputs: no named parameters.
get_articleA
Get full article detail including markdown, outline, research, and provenance
Inputs: article_id (required).
get_article_provenanceA
Get the full provenance chain: per-section facts, sources, entity QIDs, Schema.org JSON-LD
Inputs: article_id (required).
get_briefA
Get full brief detail including synthesis, enrichment, signals, and keywords
Inputs: brief_id (required).
get_coverageB
Get brief-vs-corpus coverage report for a site
Inputs: site_id (required).
get_coverage_exploreB
Get Topic Explorer data: entity clusters, coverage status, traffic, action cards
Inputs: site_id (required).
get_draftA
Get the generated draft text for a brief
Inputs: brief_id (required).
get_growth_planA
Get the latest cached growth plan for a site
Inputs: site_id (required).
get_profileA
Get a site profile by hostname (voice, topics, audience, style guide)
Inputs: hostname (required).
get_publish_statusB
Check WordPress publish status for an article
Inputs: article_id (required).
get_sourceA
Get a single source by ID, including item count
Inputs: source_id (required).
get_wordpress_statusB
Check WordPress connection status for a site
Inputs: site_id (required).
gsc_daily_summaryB
Get daily GSC performance metrics for sparklines and trends
Inputs: site_id (required).
gsc_declining_pagesB
Get pages losing search performance over time
Inputs: site_id (required).
gsc_declining_queriesB
Get GSC queries losing clicks/impressions over time
Inputs: site_id (required).
gsc_growing_pagesC
Get pages gaining search performance over time
Inputs: site_id (required).
gsc_growing_queriesB
Get GSC queries gaining clicks/impressions over time
Inputs: site_id (required).
gsc_opportunitiesA
Get GSC opportunity queries (position 4-20, high impressions)
Inputs: site_id (required).
gsc_queriesC
Get top GSC queries with performance metrics
Inputs: site_id (required), sort, limit.
gsc_summaryA
Get GSC performance summary (28-day clicks, impressions, CTR, position)
Inputs: site_id (required).
gsc_syncC
Sync Google Search Console data for a site
Inputs: site_id (required).
list_account_emailsB
List delivery email recipients
Inputs: no named parameters.
list_articlesA
List articles for a site, optionally filtered by status
Inputs: site_id (required), limit, status.
list_briefsB
List editorial briefs. Filter by site, status, signal type, or search text.
Inputs: q, limit, offset, status, +2 more.
list_corpus_documentsB
List RAG corpus documents, optionally filtered by hostname
Inputs: limit, offset, hostname.
list_deliveriesC
List email delivery history
Inputs: limit, offset.
list_sitesA
List all your sites with source and brief counts
Inputs: no named parameters.
list_sourcesB
List all content sources. Optionally filter by site.
Inputs: site_id.
populate_corpusA
Add URLs to the RAG corpus (scrapes and indexes them, max 20)
Inputs: urls (required).
populate_siteB
Populate corpus from a website sitemap
Inputs: hostname (required), max_pages.
populate_youtubeA
Populate corpus from a YouTube channel (transcripts)
Inputs: feed_url, channel_id.
publish_articleA
Publish a generated article to WordPress (requires WP credentials on the site)
Inputs: article_id (required).
rag_statsA
Get RAG corpus statistics: document counts, hostnames, coverage
Inputs: no named parameters.
regenerate_articleA
Regenerate a failed or completed article
Inputs: article_id (required).
save_wordpress_credentialsB
Connect WordPress to a site (validates connection first)
Inputs: wp_url (required), site_id (required), wp_username (required), wp_app_password (required).
search_ragA
Search the RAG corpus using semantic + keyword hybrid search
Inputs: query (required), limit.
trigger_ingestionA
Trigger content ingestion (fetches new items from RSS/YouTube/Reddit/podcast/news sources)
Inputs: source_ids.
trigger_profileA
Generate/refresh a site profile. Scrapes sitemap, analyses content. Use force=true to bypass cache.
Inputs: hostname (required), force.
trigger_synthesisB
Trigger brief synthesis (generates editorial briefs from scraped content)
Inputs: site_id.
update_articleC
Update an article (title, markdown, research, notes, keyword)
Inputs: article_id (required), title, markdown, custom_notes, +2 more.
update_siteB
Update a site name or URL
Inputs: site_id (required), url, name.
update_site_scheduleA
Update delivery schedule. Free plan: weekly only. Paid: daily/weekday/weekly_monday/weekly_friday.
Inputs: site_id (required), delivery_hour, delivery_frequency.
update_sourceA
Update a source (rename or set keyword filters)
Inputs: source_id (required), name, keywords.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 59 tools
Most tools target distinct resources (sites, sources, briefs, articles, GSC data, corpus), so an agent can usually tell them apart. However, some overlap exists: generate_article, generate_draft, and create_article all involve content creation, and the many gsc_* tools are similar in nature. Descriptions help, but a few pairs are ambiguous.
The majority of tools follow a consistent verb_noun pattern (list_*, get_*, create_*, update_*, delete_*, trigger_*). However, the gsc_* family uses noun_noun/adjective prefixes (gsc_summary, gsc_queries), and brief_feedback breaks the verb-first pattern. This mixed convention makes the API less predictable.
59 tools is a very large surface for a single MCP server. While the broad scope of content marketing automation justifies some heft, the sheer number will overwhelm agents and increase selection errors. It would benefit from splitting into focused servers or consolidating related tools.
The toolset covers the full content lifecycle: sources, briefs, drafts, articles, publishing, plus GSC analytics, RAG corpus, coverage, and growth plans. Core workflows are well-supported with no showstopper gaps. Minor omissions like no update_profile or list_drafts are workarounds rather than dead ends.
Maintenance
Related MCP Connectors
WordPress MCP server: generate SEO posts, AI images, autoblog & WooCommerce on your self-hosted site
Hosted MCP server for marketing agencies: connect Google Ads, GA4, Search Console, Meta, LinkedIn and more to Claude or ChatGPT. Pull reports and make changes via OAuth login, no setup.
A blog CMS that AI agents write into over MCP: Markdown drafts, versions, media, human approval.
WordPress MCP server: publish posts, AI images, SEO and full site management, self-hosted
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that repurposes text or URL content into platform-optimized posts for Twitter, LinkedIn, Instagram, and newsletters using AI. It enables users to automatically transform articles and blog posts into engagement-ready social media threads and professional captions.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude.ai to a Notion-based marketing knowledge base, enabling search and retrieval across specialized domains like enterprise platforms and competitive positioning. It provides tools for RAG-style Q\&A and content browsing to assist with drafting RFPs and value propositions.1-
- AlicenseBqualityDmaintenanceA high-performance MCP server designed for content creators. It automates the workflow of scraping web articles and transforming them into viral social media posts using specialized, context-aware prompt templates.22MIT
- AlicenseBqualityDmaintenanceComprehensive MCP server to manage WordPress sites via natural language, enabling content creation, SEO, and multi-site administration through AI tools like Claude Desktop.701,211 npmMIT