Skip to main content
Glama

Related Servers

Alternatives to sourcesage

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Sage 300 (beta): https://www.cdata.com/download/download.aspx?sku=GTZK-V&type=beta
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Sage 200 (beta): https://www.cdata.com/download/download.aspx?sku=GGZK-V&type=beta
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that connects to a Swagger specification and helps an AI to build all the required models to generate a MCP server for that service.
      5
      233 npm
      165
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This is an MCP server for PostgREST. It allows LLMs perform database queries and operations on Postgres databases via PostgREST. This server works with both Supabase projects (which use PostgREST) and standalone PostgREST servers.
      2,541 npm
      2,924
      Apache 2.0

    TDQS

    B3.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have distinct purposes focused on different aspects of knowledge graph management (entities, patterns, relationships, style conventions). However, there is some potential overlap between dump_project_understanding and load_project_understanding as both handle project-level data, though their descriptions clarify one is for output and the other for input.

    Naming Consistency5/5

    All tools follow a consistent snake_case naming pattern with clear verb_noun structure (e.g., add_entity_observation, get_entity_details, query_entities, register_entity). The naming is predictable and uniform across all 13 tools.

    Tool Count5/5

    With 13 tools, this is well-scoped for a knowledge graph server covering entities, patterns, relationships, and style conventions. Each tool serves a specific function in the CRUD/lifecycle operations, and none appear redundant or out of place.

    Completeness4/5

    The toolset provides comprehensive coverage for managing a knowledge graph, including registration, querying, and statistics. Minor gaps exist, such as no explicit update or delete operations for entities/patterns/relationships/conventions, but agents can work around this by re-registering or using clear_knowledge.