Skip to main content
Glama
joelgombin

MCP Wikidata Server

by joelgombin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Wikidata Server

No user-submitted related servers found.

    Related Servers

    • Wikidata MCP Server

      ebaenamar
      F
      license
      Not graded
      quality
      D
      maintenance
      Connects 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
      -

    • Wikidata MCP Server

      zzaebok
      A
      license
      A
      quality
      F
      maintenance
      A server implementation for interacting with Wikidata API using the Model Context Protocol, providing tools for searching identifiers, extracting metadata, and executing SPARQL queries.
      5
      48
      MIT

    • wikipedia

      JOBIN456
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to search Wikipedia and retrieve page content via Model Context Protocol tools, supporting natural language research.
      -

    • mcp-dbpedia

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying DBpedia's structured knowledge graph using SPARQL and lookup tools, allowing AI agents to access Wikipedia-derived data.
      5 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: find_by_property targets property-value pairs, get_entity retrieves entity details, get_relations focuses on entity relationships, search_entities handles text-based queries, and sparql_query allows custom SPARQL queries. The descriptions reinforce these distinct roles, making tool selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., find_by_property, get_entity, get_relations, search_entities, sparql_query), using snake_case uniformly. The verbs (find, get, search, execute) are appropriate to their actions, creating a predictable and readable naming convention throughout the set.

    Tool Count5/5

    With 5 tools, this server is well-scoped for interacting with Wikidata, covering essential operations like entity retrieval, searching, and querying without being overly complex. Each tool earns its place by addressing a core need in the domain, making the count appropriate for the server's purpose.

    Completeness4/5

    The tool surface provides strong coverage for querying and retrieving Wikidata data, including basic CRUD-like operations (e.g., get and search) and advanced querying via SPARQL. A minor gap exists in write operations (e.g., create or update entities), but agents can work around this given Wikidata's read-heavy nature, and the tools support most common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources