Skip to main content
Glama
manasa-manoj-nbr

semantic-context-mcp

by manasa-manoj-nbr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to semantic-context-mcp

No user-submitted related servers found.

    Related Servers

    • DB-MCP

      scrappymonkey
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that bridges AI assistants with data warehouses through Cube.js to enable governed, natural language semantic analytics queries. It provides tools for metadata discovery and secure query execution while enforcing governance policies like PII blocking and access limits.
      3
      74 npm
      1
      MIT

    • semlayer MCP server

      neocatalystlabs
      A
      license
      Not graded
      quality
      B
      maintenance
      Serves an automatically inferred semantic layer from your warehouse over MCP, enabling AI agents to query with correct business context, joins, and filters.
      1
      Apache 2.0

    • Semantic BI MCP

      LovroBubanic
      F
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server that gives AI assistants a safe, correct data-analyst capability over business metrics - without raw SQL improvisation.
      -
    • VeloDB MCP Server by velodb

      VeloDB MCP Serverofficial

      velodb
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that exposes VeloDB analytics data to AI clients through a governed semantic metrics layer (MetricFlow) and raw SQL fallback, with multi-workspace isolation, staging workflows, and a web UI for managing models.
      Apache 2.0
    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

    A4.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool addresses a distinct aspect of table understanding: search finds tables by description, describe explains meaning and columns, trace_lineage maps data flow, and check_health assesses reliability. There is no overlap between these purposes, so an agent can cleanly select the right tool for the job.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores: search_tables, describe_table, trace_lineage, check_health. The verbs are specific and the nouns clearly indicate the target resource, making the API predictable.

    Tool Count5/5

    Four tools is a tight, well-scoped set for a semantic context server focused on warehouse table understanding. Each tool covers a necessary capability without redundancy or bloat, fitting comfortably within the ideal 3-15 range.

    Completeness5/5

    The tool surface covers the complete workflow for exploring and validating tables: discover via search, inspect via describe, understand dependencies via lineage, and assess trustworthiness via health. There are no obvious missing operations that would force an agent to work around gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources