SEO content brief MCP and REST API for data-backed briefs.
Ask your AI for a brief and Cite42 returns the data: what AI already says, which sources it cites, which SEO keywords have demand, and what questions to answer.
- $1 free on signup
- Credits never expire
- No subscription
- MCP native
1. Connect once — no code Settings → Connectors → paste https://mcp.cite42.dev/ 2. Ask for the workflow Create a brief for a page about "AI visibility API for agencies". 3. Answer preview Brief the page around client reporting, prompt monitoring, citation gaps, and workflow automation. Include competitor comparisons, keyword targets, and source examples... Claude can still inspect the endpoint plan cite42_generate_content_brief → /v1/workflows/content-brief Then it can call the primitives Use /v1/search, /v1/citations, /v1/keywords (each source is status-labelled in the JSON)
Run the Content brief workflow.
Your AI gets the workflow endpoint, source icons, and endpoint plan before it runs the endpoint calls.
Content brief
You ask your AICreate a brief for a page about "AI visibility API for agencies".MCP runs/v1/workflows/content-brief
- /v1/search
- /v1/citations
- /v1/keywords
- /v1/trends
- /v1/reddit/trends
- /v1/youtube/trends
Your AI saysCite42 returns a workflow plan for content brief. It lists the endpoints to run, why they matter, and what your AI should check next...Which endpoints to run
You ask your AIWhich Cite42 data should I check for content brief?MCP runs/v1/workflows/content-brief
- /v1/search
- /v1/citations
- /v1/keywords
- /v1/trends
- /v1/reddit/trends
- /v1/youtube/trends
Your AI saysStart with /v1/search, /v1/citations, /v1/keywords. The plan marks which sources are live, what each endpoint returns, and how to combine the evidence...
Brief from market data first.
Use this workflow when a writer or AI agent needs evidence before drafting: AI answers, citations, keywords, trends, Reddit questions, and YouTube angles.
- Collect the evidence before writing.
- Keep research sources visible in the brief.
- Use the same plan for blog posts, pages, and scripts.

Sources Cite42 checks.
Cite42 queries AI answers, search demand, and conversation signals, then returns normalized results your app or agent can use.
ChatGPT
AI answer signal
Claude
AI answer signal
Perplexity
AI answer signal
Gemini
AI answer signal
Google AI Overviews
Search answer signal
Google data
Search demand signal
Reddit
Conversation signal
YouTube
Video demand signal
Three ways to use this workflow.
A few practical ways teams use the Content brief workflow.
What endpoints the workflow uses.
Each card shows the primitive API endpoint, source coverage, why the workflow uses it, and the data it returns.
AI search
Shows what AI models already say about the topic.
Data returned
Per-model answers, cited URLs, source titles, and latency.
AI citations
Finds which sources AI models cite and where your site is missing.
Data returned
Cited URLs, cited-by model list, citation counts, and source titles.
SEO keywords
Adds search volume, CPC, competition, and related keyword ideas.
Data returned
Search volume, CPC, competition, intent, and related SEO keyword ideas.
Google Trends
Shows whether demand is rising, flat, or fading.
Data returned
Interest over time, trend direction, rising queries, and top related queries.
Reddit trends
Adds repeated questions, pain points, and language from Reddit.
Data returned
Rising threads, repeated questions, pain points, repeated phrases, and source URLs.
YouTube trends
Adds video angles, title patterns, and creator-market signals.
Data returned
Rising videos, title patterns, channel examples, creator angles, and format ideas.
Pay per call for this workflow.
Top up once ($25 minimum). Credits never expire, and this workflow only charges when it runs.
| Endpoint | Price | What you get |
|---|---|---|
| POST/v1/workflows/content-brief | $0.28-$0.58 | Workflow plan plus 6 primitive endpoint calls. |
All workflows
Same MCP server, same REST API, different research job.
Questions about Content brief.
Give your AI the market data.
Install the MCP server or call the workflow endpoint directly. One call runs every primitive and the per-source results stay visible.