Marketing
curiositygraph.com
An SEO and content research MCP server that surfaces ranked search questions, keyword tags, question graphs, and generates structured article briefs for topics.
ENDPOINT 1
https://curiositygraph.com/mcp
MCP server metadata
- Name
- curiositygraph
- Version
- 1.0.0
Known tools 5
research_topicGet the ranked map of real questions people search about a topic (cached corpus).
Inferred read-onlyget_tagsGet the real keyword tags (with search volume) associated with a charted topic.
Inferred read-onlyexpand_questionExpand a question into related sibling questions or narrower sub-questions within a charted topic.
Inferred read-onlygenerate_briefGenerate a structured article brief (title, H2/H3 outline, FAQ) from specific cluster ids.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.curiositygraph]
url = "https://curiositygraph.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"curiositygraph": {
"type": "http",
"url": "https://curiositygraph.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: curiositygraph
Remote MCP URL: https://curiositygraph.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"curiositygraph": {
"url": "https://curiositygraph.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"curiositygraph": {
"type": "http",
"url": "https://curiositygraph.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "curiositygraph",
"transport": "streamable-http",
"url": "https://curiositygraph.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.