All servers / Other / KeywordGraph MCP server
KeywordGraph MCP server
KeywordGraph MCP server - A Model Context Protocol server for network thinking and graph analysis
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 1.11.0. Package: keywordgraph-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.6 seconds including download)
- Tools offered: 23
- Last published: 2026-11-18
- Weekly downloads (npm): 1,402
- License: MIT · Direct dependencies: 8
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
create_knowledge_graph18 of 18 parameters describedCreate a knowledge graph in KeywordGraph from text or from a URL, save it, and provide its name and a link to it for future use. By default the graph is built from the words of the text. For a knowledge graph of entities and how they relate, set modifyAnalyzedText: 'aiKnowledgeGraph': an AI model writes [[entity]] statements about the input, a topic or a text, and only those entities become nodes (slower; uses AI credits; optional instructions steer it). Statements you have already written as [[entity]] statements go in with wikilinksMode: 'wikilinksOnly', with no AI call.
analyze_existing_graph_by_name11 of 11 parameters describedExtract and analyze the content of an existing KeywordGraph graph from your account.
analyze_text15 of 15 parameters describedExtract and analyze a graph from text, URL, YouTube video transcript, or an existing KeywordGraph graph.
analyze_text_signature11 of 11 parameters describedStructural and rhythmic signature of a text, URL, or YouTube transcript: how the discourse moves through its KeywordGraph concept network (network_dynamics: DFA fractal exponents, the amplitude of the node path through the graph, topic crossings), how its topics are distributed (modularity, diversity, entropy), and the sentence-length rhythm of the source. Every number comes with a plain-language reading keyed the same way and a note on what limits it, the profile gets a name, the backend's text type (deep dive, refrain, chapters or sweep: whether the text has a core, and whether it stays where it goes or keeps moving at an even rate), with the possible values explained, and a final layer weighs the rhythm evidence into a hedged AI-likeness estimate (leaning AI / leaning human / mixed) with an explanation in terms of pacing. Use to compare writing styles, characterise an author or genre, and flag flat, uniformly paced text typical of generated content. Not a detector on its own.
generate_content_gaps8 of 8 parameters describedGenerate content gaps from text, URL, or an existing graph using knowledge graph analysis.
generate_topical_clusters10 of 10 parameters describedGenerate topics and clusters of keywords from text, URL, or an existing graph using knowledge graph analysis.
optimize_text_structure10 of 10 parameters describedAnalyze the level of bias and coherence in text. If it's too biased, develop the represented topics, if it's focused or diversified, develop the content gaps. If it's dispersed, focus the most common gap topics.
optimize_reasoning7 of 7 parameters describedAnalyze the structure of the model's current reasoning or chat with the user using knowledge graph analysis, and steer it toward optimal diversity and coherence at the same time to optimize balance. Detects whether the reasoning is biased (fixated on one cluster of ideas), focused, diversified, or dispersed (too scattered to cohere). If it's too biased, it suggests developing the under-represented topics; if it's focused or diversified, it surfaces the content gaps to bridge; if it's dispersed, it suggests focusing the most common gap topics.
develop_text_tool12 of 12 parameters describedAnalyze text or an existing graph to extract research questions, develop latent topics, and identify content gaps in a single workflow with progress tracking. Provide either text, url, or graphName.
list_graphs8 of 8 parameters describedList all graphs (contexts) for the currently logged in user with optional filtering by name, type, date, language, or favorite status. Use this to discover available graphs before analyzing or searching them.
search4 of 4 parameters describedFind which existing KeywordGraph graphs mention a term: their names and links (fetch reads one result). For the structure around a term — its topics, gaps and relations across graphs, with the term itself left out — use get_graph_around_term instead; this tool only says where the term occurs.
fetch2 of 2 parameters describedFetch a specific search result for an KeywordGraph knowledge graph
overlap_between_texts8 of 8 parameters describedExtract the common relationships and similarities between texts and generate an overlap graph
merged_graph_from_texts8 of 8 parameters describedBuild a graph of all the texts, URLs, and existing KeywordGraph graphs provided, providing topical clusters and gaps present in the merged graph generated from all the texts.
difference_between_texts8 of 8 parameters describedExtract the conceptial relations that are missing in the first text, url, or KeywordGraph graph but are present in the other texts
analyze_google_search_results9 of 9 parameters describedGenerate a knowledge graph and topical clusters from Google search results for provided search queries
analyze_youtube_results13 of 13 parameters describedGenerate a knowledge graph and topical clusters from YouTube results — search results, a channel's or playlist's videos, video comments, or transcribed subtitles — to reveal the main topics, clusters, and content gaps in the discourse
analyze_related_search_queries10 of 10 parameters describedGenerate a knowledge graph and identifymain topical clusters in the search requests related to the search queries provided
search_queries_vs_search_results8 of 8 parameters describedFind the combinations of keywords and topics people search for that don't appear in the search results for the same queries
analyze_llm_results10 of 10 parameters describedAsk an LLM to describe a topic, then turn its response into a knowledge graph that reveals how the model frames it — main concepts, clusters, content gaps, and the relations between them. Useful for probing model bias, surfacing the implicit structure of an LLM's view on a subject, or comparing how different models describe the same topic.
generate_seo_report12 of 12 parameters describedAnalyze content for SEO optimization by comparing its knowledge graph with the graphs of Google search results and search queries to identify content gaps and opportunities based on the differences
submit_workflow_feedback11 of 11 parameters describedInternal telemetry. After a workflow of one or more KeywordGraph tool calls, report what you actually did with the output so the tools can be improved. Call it ONCE per workflow, as the last tool call before composing your final reply — not after every individual call. Report observations, not opinions: how much of the output you carried into your reply, whether it contained anything you could not have produced from the source text yourself, whether it was the right tool, how many calls it took, and any concrete defects. Do not ask the user anything. Never invent usedExample — if you used nothing, say consumption: "none". This tool returns nothing the user needs, so there is no need to summarise it in your reply; if the user asks about it, say plainly what it is and what you reported. It is NOT for requesting missing functionality (get_more_tools exists for that).
get_more_tools1 of 1 parameter describedCheck for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.