Auto Ontology MCP
Related Servers
Alternatives to Auto Ontology MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceEnables natural language querying of SQL databases and REST APIs through the MCP protocol, grounded in a semantic layer.243 npm1AGPL 3.0- AlicenseNot gradedqualityDmaintenanceEnables natural language querying of SQLite databases through a secure MCP server that writes, runs, and explains SQL with a three-layer read-only guarantee.MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural-language querying of Postgres and MongoDB databases in read-only mode, with PII masking and row/timeout guardrails, from any MCP client.-
- FlicenseNot gradedqualityBmaintenanceEnables governed, read-only SQL analytics, hybrid RAG knowledge search, financial metric calculation, and database schema introspection through MCP, with role-based access control, audit logging, and AI observability.-
- AlicenseNot gradedqualityBmaintenanceProvides read-only, guarded access to business databases via MCP. Enables natural language querying with built-in security barriers like table allowlists, PII masking, and audit logging.MIT
- AlicenseNot gradedqualityBmaintenanceServes an automatically inferred semantic layer from your warehouse over MCP, enabling AI agents to query with correct business context, joins, and filters.3Functional Source , Version 1.1, ALv2 Future
TDQS
Scored across 33 tools
Most tools target distinct operations, but several search/retrieval tools overlap: search_ontology, search, fetch, get_term, list_terms and describe_table can all surface Term or table information. Similarly, define_entity, save_concept, save_table_terms and update_term all create/update Terms in different scopes, forcing the agent to reason carefully about which one to use.
Predominantly verb_noun (get_term, save_sql_attribute, validate_sql, find_join_path), with only minor deviations like recent_changes, search and fetch. The convention is predictable overall.
With 33 tools, the surface is well above the 3–15 sweet spot and includes redundant search/read tools. Although the domain is broad, the set feels overgrown and could be consolidated.
Covers datasource registration/scanning, Term modeling, relationships, SQL attributes, glossary, query validation/execution, export/import, personal knowledge records, concepts, sources and wiki export. Minor gaps include no delete-datasource operation and no explicit datasource listing beyond check_readiness.