fred-capability-mcp 4.4.3__py3-none-any.whl

fred_capability_mcp/__init__.py

@@ -0,0 +1,13 @@
+# Copyright Thales 2026
+# SPDX-License-Identifier: Apache-2.0
+"""Installed MCP catalog provider, built entirely on fred-sdk."""
+
+from fred_sdk.contracts.services import ServiceEndpointsPort
+from fred_sdk.resources.mcp import McpCatalog, load_packaged_mcp_catalog
+
+
+def load_catalog(services: ServiceEndpointsPort) -> McpCatalog:
+    """Load the MCP servers provided by Fred."""
+    return load_packaged_mcp_catalog(
+        package=__name__, path_parts=("mcp_catalog.yaml",), services=services
+    )

fred_capability_mcp/mcp_catalog.yaml

@@ -0,0 +1,37 @@
+version: v1
+
+# MCPs provided by Fred / Knowledge Flow.
+servers:
+  - id: "mcp-knowledge-flow-mcp-tabular"
+    name: "mcp.servers.tabular.name"
+    description: "mcp.servers.tabular.description"
+    prompt_group_title: "tabular action"
+    transport: "streamable_http"
+    service: knowledge_flow
+    path: mcp-tabular
+    sse_read_timeout: 2000
+    enabled: true
+    auth_mode: "delegated"
+    prompt_file: pkg://fred_capability_mcp/prompts/tabular.md
+
+  - id: "mcp-knowledge-flow-opensearch-ops"
+    name: "mcp.servers.search_opensearch.name"
+    description: "mcp.servers.search_opensearch.description"
+    prompt_group_title: "OpenSearch operations"
+    transport: "streamable_http"
+    service: knowledge_flow
+    path: mcp-opensearch-ops
+    sse_read_timeout: 2000
+    enabled: true
+    auth_mode: "delegated"
+
+  - id: "mcp-knowledge-flow-prometheus-ops"
+    name: "mcp.servers.prometheus.name"
+    description: "mcp.servers.prometheus.description"
+    prompt_group_title: "Prometheus operations"
+    transport: "streamable_http"
+    service: knowledge_flow
+    path: mcp-prometheus-ops
+    sse_read_timeout: 2000
+    enabled: true
+    auth_mode: "delegated"

fred_capability_mcp/prompts/tabular.md

@@ -0,0 +1,82 @@
+## Tabular data access (read-only SQL over ingested spreadsheets)
+
+These tools give read-only SQL access to ingested tabular documents: CSV
+files (one table each) and Excel workbooks (one or several extracted
+tables), stored as Parquet and queried through DuckDB.
+
+Follow this order before answering a data question — do not guess table or
+column names. Use only the tools you need for the user's request, but
+NEVER skip `describe_tabular_documents` before `read_query`.
+
+1. `list_tabular_documents` — returns each accessible CSV or Excel document's
+   name and `document_uid`. Excel entries also list their tables with
+   sheet/title when available and the exact SQL `query_alias`. CSV entries
+   have no table list; use their `document_uid` for schema inspection.
+   An alias shown here is for locating a table, not for querying it yet.
+2. `describe_tabular_documents` — pass one or several document UIDs. For
+   Excel, read each document's `markdown` catalog first to identify the
+   relevant sheet and table: it includes titles, context, data ranges,
+   exact SQL aliases and residual text. Then inspect the selected table's
+   structured `columns` to confirm exact names and types. CSV documents
+   have no markdown catalog; use their typed table description directly.
+   Before `read_query`, you MUST call this tool with all document UIDs to
+   be queried (one call can include several UIDs) and obtain each SQL
+   table name from its `tables[].query_alias`, even if
+   `list_tabular_documents` already showed an alias.
+3. `read_query` — run ONE read-only SELECT over the mounted tables. In
+   the SQL, refer to EVERY table in `FROM` or `JOIN` by its exact
+   `tables[].query_alias` from step 2; do not use a
+   `document_uid`, filename, sheet name or table title as the SQL table
+   name. Joins across several tables are supported, including tables from
+   different documents, as long as each document is mounted via
+   `dataset_uids`.
+4. `search_tabular_values` — a LAST-RESORT locator for when a workbook (or
+   corpus) has many tables and you cannot tell from the catalog which one
+   holds a specific value the user named (a reference code, a name, an
+   amount). For Excel workbooks, use it only AFTER step 2: never call it
+   before reading the markdown catalog, and never to discover what a
+   workbook contains — step 2 already does that. Give it ONE precise
+   keyword (matching ignores case, accents and spaces and covers numeric
+   columns); it returns the table(s) and column(s) holding that value plus
+   a few matching rows, so you can then run one targeted `read_query`
+   (step 3). Use it sparingly — a generic term matches too many tables and
+   cannot disambiguate; if the response sets `tables_truncated` or a
+   table's `row_truncated`, the result is partial, so refine the keyword or
+   go back to the catalog.
+
+Always scope `read_query` with `dataset_uids` (document uids — one
+spreadsheet uid mounts every table of the workbook). `dataset_uids`
+selects documents to mount; `query_alias` identifies each table in SQL.
+
+The `query_alias` returned by `describe_tabular_documents` is an internal
+technical identifier, used ONLY to build your queries. NEVER expose a
+`query_alias` to the user or mention it in your answer. When you refer to
+a table or sheet, use its human-readable name — the sheet or table title —
+not its `query_alias`.
+
+For Excel workbooks only: the markdown catalog from
+`describe_tabular_documents` lists every sheet, table, data range and
+identified column of the workbook. When — and only when — that catalog
+makes clear beyond any doubt that the workbook holds nothing about what the
+user asks (no column, table or context relates to the concept), answer that
+the information is absent and do NOT run `read_query`. If any doubt remains,
+query instead of guessing. This shortcut requires having read the markdown
+first and applies to Excel only — plain CSV documents have no markdown
+catalog, so confirm their columns in the typed table description.
+
+When you do query, only use `LIKE`/`ILIKE` on text columns. Never apply
+`LIKE` to a numeric column — DuckDB rejects it with a binder error and the
+query fails. Filter numeric columns with `=`, `<`, `>` or ranges, and
+confirm each column's type before writing the WHERE clause — the
+structured `columns` in `describe_tabular_documents` report these types.
+For string columns with `is_categorical=true`, `sample_values` lists every
+distinct non-null value found. Use the exact stored spelling in filters;
+`has_two_values=true` reports two distinct strings, not a boolean type or
+true/false semantics. Only `dtype=boolean` confirms a typed boolean column.
+For `dtype=integer` and `dtype=float`, `min_value` and `max_value` give
+the finite observed bounds when available. Use them to understand the
+data range before choosing numeric filters; they are descriptive, not
+a substitute for `read_query` when the user needs actual rows or counts.
+
+Only read-only SELECT queries are available. Never attempt INSERT, UPDATE,
+DELETE, DROP, ALTER, or TRUNCATE — no write operations exist on these tables.

fred_capability_mcp-4.4.3.dist-info/METADATA

@@ -0,0 +1,69 @@
+Metadata-Version: 2.4
+Name: fred-capability-mcp
+Version: 4.4.3
+Summary: Catalog and packaged agent instructions for Fred's existing MCP capabilities.
+Author-email: Thales <noreply@thalesgroup.com>
+License: Apache-2.0
+Requires-Python: <3.13,>=3.12
+Description-Content-Type: text/markdown
+Requires-Dist: fred-sdk[agents]>=4.4.3
+Provides-Extra: dev
+
+# MCP capability catalog and instructions
+
+Installing this package supplies Fred's internal MCP servers at pod startup through
+its `fred.mcp_catalogs` entry point (`fred_capability_mcp:load_catalog`). The loader
+uses `fred_sdk.resources.mcp`; capability construction, composer controls and
+prompt groups live in `fred_sdk.contracts.capability.mcp`. The package has no
+`fred-runtime` dependency.
+
+The runtime resolves one catalog for transport and capability registration.
+`FRED_MCP_CATALOG_FILE` or an existing `./config/mcp_catalog.yaml` replaces all
+packaged servers. Otherwise it combines installed providers with the optional
+`FRED_MCP_EXTERNAL_CATALOG_FILE` or `./config/mcp_catalog_external.yaml` file.
+Duplicate server IDs fail startup.
+
+The wheel includes one `mcp_catalog.yaml` with the three MCPs provided by
+Fred / Knowledge Flow. Third-party MCP servers are not defined by this package.
+
+Internal HTTP MCPs declare their backend and a path relative to its API:
+
+```yaml
+service: knowledge_flow
+path: mcp-tabular
+```
+
+`fred_sdk.contracts.services` defines `FredService` and `ServiceEndpointsPort`.
+At boot, the runtime passes `ConfiguredServiceEndpoints` to each catalog loader.
+Its `get_base_url(service)` reads `ai.knowledge_flow_url` or
+`platform.control_plane_url`, preserving the configured scheme, host, port and API
+prefix. For example, `https://kf.example:9443/custom/v2/` produces
+`https://kf.example:9443/custom/v2/mcp-tabular`. No address is stored in the
+package catalog. Local document search is supplied by the native `document_access`
+capability; the MCP catalog no longer advertises that tool or the unimplemented
+GitHub adapter. Local tools use capabilities rather than an MCP transport.
+
+External catalogs may use the same references by passing `services` to the SDK
+loader, or retain a concrete `url`. Do not combine `service` with `url`.
+Unknown services, missing addresses and invalid HTTP paths fail catalog loading.
+SDK-only callers supply their own implementation of the port; no runtime import
+or network discovery is required.
+
+The wheel also includes `prompts/tabular.md`, the default pod's tabular instructions.
+
+Deployment-owned catalogs can reference these instructions using:
+
+```yaml
+prompt_file: pkg://fred_capability_mcp/prompts/tabular.md
+```
+
+Inline `agent_instructions` remains supported. File references also accept
+absolute paths or paths relative to the catalog. A packaged catalog resolves
+relative paths within the package, including when imported from a wheel.
+Declare only one instruction source; unreadable resources fail startup.
+
+`fred-agents` installs this package locally and in its image; no copied catalog
+or checkout symlink is needed. The Fred chart mounts an additional external
+catalog while the installed package supplies its internal servers. Other pods
+can provide their own MCP catalogs through the SDK/runtime interfaces. No extra
+selectable wrapper capability is introduced: enabled servers retain their IDs.

fred_capability_mcp-4.4.3.dist-info/RECORD

@@ -0,0 +1,8 @@
+fred_capability_mcp/__init__.py,sha256=zFFYQByF__j9SIjGLhFLNoS_Wa_zEGL9YVl2v3coV8w,500
+fred_capability_mcp/mcp_catalog.yaml,sha256=k4bU84ix3yl1PnqynqnYUuSXCSdl8nojbpJj23fZjrU,1163
+fred_capability_mcp/prompts/tabular.md,sha256=YhK0A3Lr9lfLGkm-ZIewmO3qNF59fk_uUim-BRCi6CI,5125
+fred_capability_mcp-4.4.3.dist-info/METADATA,sha256=oxzSnaQ2-VIT8vIpgOkSDIGhZL97zppw_GkCnByGDe8,3328
+fred_capability_mcp-4.4.3.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+fred_capability_mcp-4.4.3.dist-info/entry_points.txt,sha256=GUYuUSziAJUxdcmVWbDClwuF8d7EbClqJ5aXIR8zi9E,59
+fred_capability_mcp-4.4.3.dist-info/top_level.txt,sha256=Sr4l6JSaAUOFn6vvumiWPtBMGslXHOF_CRTCtQf_vDU,20
+fred_capability_mcp-4.4.3.dist-info/RECORD,,

fred_capability_mcp-4.4.3.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

fred_capability_mcp-4.4.3.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[fred.mcp_catalogs]
+mcp = fred_capability_mcp:load_catalog

fred_capability_mcp-4.4.3.dist-info/top_level.txt

@@ -0,0 +1 @@
+fred_capability_mcp