[Candidate / unverified] TG-based information systems lack a supported Model Context Protocol (MCP) server, so LLM clients cannot use standard MCP resources and tools to query TG application data.

## Support semantics This is a **candidate / unverified** Solution from the KFA continuous knowledge loop. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause MCP is a client-server standard where LLMs consume read-only resources and callable tools. TG exposed application data through GraphQL Web API without an MCP adapter, creating a protocol gap for LLM tooling. The issue specifies platform-mcp to start an MCP server with resource tg://query-guide and tool execute_query that runs GraphQL against the running application, after structured domain introspection, composite key field, aggregation roots, and where-based filtering are available in GraphQL. ## Steps 1. Add a platform-mcp dependency to the app-web-server Maven module. 2. Install McpIocModule in the application web server IoC module (typically WebApplicationServerIocModule). 3. Override registerUnguardedDomainWebResources in WebUiResources to register IMcpWebUiResources when present. 4. Configure mcp.resource.path, supply web.api.key.mcp as a JVM option or environment variable, and set mcp.user to an existing application user key. 5. Point MCP HTTP clients at the configured MCP path and send the API key in the X-API-Key header. 6. Use the tg://query-guide resource and execute_query tool for GraphQL data access; migrate filters from per-field arguments to the where argument where applicable. ## Source evidence - https://github.com/fieldenms/tg/issues/2856 (2026-10-03T17:27:08.000Z) — evidence_class: PRIMARY — Title: Support for Model Context Protocol (OPEN). Goal: add MCP to TG so LLMs interact with TG-based systems. Maven modu ## Evidence claims - (primary_source) The stated goal is to add MCP support to TG via Maven module platform-mcp so LLMs can interact with TG-based systems. — https://github.com/fieldenms/tg/issues/2856 - (primary_source) The MCP server should expose tool execute_query to run GraphQL queries against the running application, making GraphQL the LLM query path. — https://github.com/fieldenms/tg/issues/2856 - (primary_source) Resource tg://query-guide loads from classpath file /mcp/graphql-query-guide.md under platform-mcp/src/main/resources/mcp. — https://github.com/fieldenms/tg/issues/2856 - (primary_source) The MCP web resource uses API-key authentication via HTTP header X-API-Key instead of the standard username-password web guard, and requests run as the configured mcp.user. — https://github.com/fieldenms/tg/issues/2856 - (primary_source) GraphQL breaking changes include removing field-argument conditions in favor of where, rejecting duplicate field selections below root, and rejecting conditions on collectional properties. — https://github.com/fieldenms/tg/issues/2856 - (primary_source) Claude Code may fail with DEPTH_ZERO_SELF_SIGNED_CERT against self-signed TLS; the issue documents NODE_TLS_REJECT_UNAUTHORIZED=0 for development only. — https://github.com/fieldenms/tg/issues/2856 ## Limitations - Primary source is an open GitHub feature and design issue, not an end-user failure report with reproduction logs. - Integration steps assume the standard TG web server layout (WebUiResources, IoC modules, GraphQL Web API). - Claude Code self-signed certificate guidance uses NODE_TLS_REJECT_UNAUTHORIZED=0 and is explicitly development-only. - Issue documents breaking GraphQL filter API changes; migration effort for existing Web API clients is not quantified in the source. ## Unknowns - No dotted numeric TG or platform-mcp release version is stated in the issue body at retrieval time. - Merge and ship status of the platform-mcp Maven module relative to a tagged public release is not established from this issue alone. - Whether a specific TG application has completed the four documented integration steps cannot be determined from the issue. - Production hardening beyond API-key authentication and configured mcp.user is not specified in the excerpted source. ## Freshness - retrieved_at: 2026-10-06T22:51:00.000Z