You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,6 +113,15 @@ Every tool call is logged with user identity, persona, request details, and timi
113
113
### Knowledge Capture
114
114
AI sessions generate valuable domain knowledge: column meanings, data quality issues, business rules. The `capture_insight` tool records these observations during sessions, and `apply_knowledge` provides admins with a structured review workflow. Approved insights are written back to DataHub with full changeset tracking and rollback. An [Admin REST API](https://txn2.github.io/mcp-data-platform/knowledge/admin-api/) supports integration with existing governance tools. See the [Knowledge Capture documentation](https://txn2.github.io/mcp-data-platform/knowledge/overview/) for details.
115
115
116
+
### Resource Templates
117
+
Browse platform data as parameterized MCP resources using RFC 6570 URI templates. Three built-in templates expose table schemas (`schema://catalog.schema/table`), glossary terms (`glossary://term`), and data availability (`availability://catalog.schema/table`) without making tool calls.
118
+
119
+
### Progress Notifications
120
+
Long-running Trino queries send granular progress updates to MCP clients (executing, formatting, complete). Clients that provide a `_meta.progressToken` receive real-time status. Zero overhead when disabled.
121
+
122
+
### Client Logging
123
+
Server-to-client log messages give AI agents visibility into platform decisions (enrichment applied, timing). Uses the MCP `logging/setLevel` protocol — zero overhead if the client hasn't opted in.
124
+
116
125
### Extensible Middleware Architecture
117
126
Add custom authentication, rate limiting, or logging. Swap providers to integrate different semantic layers or query engines. The Go library exposes everything—build the platform your organization needs.
Copy file name to clipboardExpand all lines: docs/llms-full.txt
+34Lines changed: 34 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,12 @@ The only requirement is DataHub (https://datahubproject.io/). Add Trino (https:/
26
26
27
27
- **Personas**: Define who can use which tools. Analysts get read access. Admins get everything. Map from your identity provider's roles.
28
28
29
+
- **Resource Templates**: Browse platform data as parameterized MCP resources using RFC 6570 URI templates. Three built-in templates: table schemas (`schema://catalog.schema/table`), glossary terms (`glossary://term`), and data availability (`availability://catalog.schema/table`).
30
+
31
+
- **Progress Notifications**: Long-running Trino queries send granular progress updates (executing, formatting, complete) to clients that provide `_meta.progressToken`. Zero overhead when disabled.
32
+
33
+
- **Client Logging**: Server-to-client log messages for platform decisions (enrichment, timing) via MCP `logging/setLevel` protocol. Zero overhead if the client hasn't opted in.
34
+
29
35
---
30
36
31
37
# The Data Stack: DataHub + Trino + S3
@@ -288,6 +294,33 @@ No patterns configured means all tools are visible. When both are set, allow is
288
294
289
295
When `admin.portal: true`, an interactive web dashboard is served at the admin path prefix. It provides audit log exploration, tool execution testing, and system monitoring.
When enabled, Trino query tools send three progress notifications per query: before execution, after query returns, and after formatting. Clients must include `_meta.progressToken` in their tool call to receive notifications.
When enabled, the platform sends log notifications to clients after enrichment is applied (tool name, duration). Uses MCP `logging/setLevel` protocol — zero overhead if the client hasn't called `setLevel`.
323
+
291
324
## Audit Configuration
292
325
293
326
| Field | Type | Default | Description |
@@ -1001,6 +1034,7 @@ Use the library when you need to:
Copy file name to clipboardExpand all lines: docs/llms.txt
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@
11
11
- [Home](index.md): Introduction, quick start, and key features
12
12
- [Server Overview](server/overview.md): What the platform does, architecture, request flow
13
13
- [Installation](server/installation.md): Install via go install, Homebrew, Docker, or from source
14
-
- [Configuration](server/configuration.md): YAML configuration with environment variable expansion, config versioning (apiVersion field, version lifecycle, migrate-config CLI), config store options (file vs database mode), tool visibility filtering (allow/deny patterns for tools/list token reduction), admin API and portal, database, audit, and session configuration
14
+
- [Configuration](server/configuration.md): YAML configuration with environment variable expansion, config versioning (apiVersion field, version lifecycle, migrate-config CLI), config store options (file vs database mode), tool visibility filtering (allow/deny patterns for tools/list token reduction), resource templates, progress notifications, client logging, admin API and portal, database, audit, and session configuration
15
15
- [Operating Modes](server/operating-modes.md): Three deployment modes — standalone (no database), full-config file + database, bootstrap + database config. Feature availability by mode, example configurations, decision guide
16
16
- [Admin Portal](server/admin-portal.md): Built-in web dashboard for monitoring and managing the platform. Dashboard with activity timelines, performance percentiles, error monitoring. Tools overview with connection grid and tool inventory. Interactive tool explorer with semantic enrichment display. Searchable audit log with event detail drawer. Knowledge insight governance with approve/reject workflow and changeset tracking. Local dev with MSW mock data
17
17
- [Admin API](server/admin-api.md): REST endpoints for system info, config management, personas, auth keys, audit, knowledge. Authentication, operating mode behavior, request/response reference. Interactive Swagger UI at `/api/v1/admin/docs/`
@@ -73,7 +73,7 @@
73
73
- [Tools API](reference/tools-api.md): Complete tool specifications with parameters and responses
74
74
- [Configuration](reference/configuration.md): Full YAML schema with all options
75
75
- [Providers](reference/providers.md): Semantic, query, and storage provider interfaces
76
-
- [Middleware](reference/middleware.md): Request processing chain including tool visibility middleware
0 commit comments