Skip to main content
Glama
Band-Aid

Pendo Ontology MCP Server

by Band-Aid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Pendo Ontology MCP Server

No user-submitted related servers found.

    Related Servers

    • semlayer MCP server

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

      EnrichMCPofficial

      featureform
      A
      license
      Not graded
      quality
      D
      maintenance
      Turns your data model into a semantic layer for AI agents, automatically generating typed, discoverable tools with entity relationships and schema discovery.
      644
      Apache 2.0

    • RunContext

      Quiet-Victory-Labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to understand and query your database safely by providing a semantic layer of metadata, with tools to search, explain, validate, and generate safe SQL.
      2
      MIT

    • Understory

      PolycultureResearch
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables employees to ask natural-language questions about a client's dbt semantic layer through the chatbot they already use, asking for clarification when needed, refusing when data can't answer, and logging every interaction so the semantic layer improves over time.
      1
      MIT
    • Foggy Data MCP Bridge by foggy-projects

      Foggy Data MCP Bridgeofficial

      foggy-projects
      A
      license
      Not graded
      quality
      D
      maintenance
      A semantic layer query engine with MCP support, enabling AI assistants to query structured data through natural language and declarative interfaces.
      2
      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.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but get_concept and lookup_ontology both return full concept details, and the three entity ingestion methods (register_entities, ingest_pendo_payload, sync_from_pendo) could confuse agents despite clear descriptions. Overall, the boundaries are well-defined.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (list_, get_, lookup_, upsert_, delete_, suggest_, register_, ingest_, sync_). The naming is predictable and makes the action and resource clear.

    Tool Count5/5

    With 11 tools, the server is well-scoped for ontology management. Each tool covers a distinct aspect (concepts, entities, links, ingestion, discovery) without redundancy or bloat.

    Completeness5/5

    The tool set provides comprehensive coverage: concept CRUD (upsert_concept, delete_concept, get_concept), ontology overview/search (get_product_map, lookup_ontology), entity cataloging and registration (get_entity_catalogue, register_entities, ingest_pendo_payload, sync_from_pendo), link suggestions (suggest_links), and gap analysis (list_coverage_gaps). No obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources