Google Knowledge Graph MCP
Related Servers
Alternatives to Google Knowledge Graph MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables users to search, rank, and compare Google Knowledge Graph entities, audit knowledge panel readiness with Wikidata connections, and generate JSON-LD schema for brands or people.42MIT
- FlicenseNot gradedqualityAmaintenanceEnables querying Google, Bing, Yahoo, DuckDuckGo, YouTube, eBay and many other search engines for real-time results, weather, stock data and more, returning structured JSON or token-efficient Markdown. It also exposes per-engine parameter schemas as resources and offers opt-in interactive table and dashboard views.-
- FlicenseNot gradedqualityAmaintenanceEnables querying Google, Bing, Yahoo, DuckDuckGo, YouTube, eBay, and other engines for live search results, weather, stock data, and structured data extraction, with selectable JSON or token-efficient Markdown responses. It also exposes per-engine parameter schemas as resources and can render results in interactive UI views.-
- AlicenseNot gradedqualityBmaintenanceEnables querying DBpedia's structured knowledge graph using SPARQL and lookup tools, allowing AI agents to access Wikipedia-derived data.130 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search Google for web results, images, videos, news, products, scholarly articles, and patents, plus local business lookup with contact details and ratings, and full text extraction from any page, accepting up to 100 queries in a single call.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to perform live Google searches and retrieve structured SERP data including organic results, AI Overviews, People Also Ask, AI Mode answers, news, shopping, and short-video results via eight read-only tools.1068 npm14MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches by name/topic, the other retrieves by specific MID. There is no overlap in functionality, and an agent can easily choose the right tool based on whether it has an ID or a query.
Both tools follow a verb + 'knowledge_graph' pattern, with 'search_knowledge_graph' and 'lookup_knowledge_graph_entities'. The second includes an extra noun ('entities'), but the shared prefix and consistent style make them predictable and readable.
With only two tools, the server feels minimal but functional for its stated purpose of querying the Knowledge Graph. It falls into the borderline range where the count is thin but not unreasonable for a focused utility.
The two core operations for a knowledge graph API—search and lookup by ID—are covered. Missing features like batch lookup or relation traversal are minor gaps that can be worked around with repeated calls.