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.41MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying DBpedia's structured knowledge graph using SPARQL and lookup tools, allowing AI agents to access Wikipedia-derived data.164 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
- AlicenseAqualityAmaintenanceEnables 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.10272 npm178 PyPI18MIT
- AlicenseAqualityDmaintenanceEnables searching and retrieving content from Grokipedia, with tools for page lookup, citations, sections, and related pages.7MIT
- FlicenseNot gradedqualityDmaintenanceConnects LLMs to Wikidata's structured knowledge base using a hybrid architecture that optimizes for both fast entity searches and complex relational queries. It provides tools for entity and property retrieval, metadata lookups, and direct SPARQL execution to ground AI responses in verified data.2-
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.