FA-Technician-Brain-MCP

A Model Context Protocol (MCP) knowledge server for the Technician Portal module in FleetFocus FA/EAM (InfoCenter). This server provides structured, queryable information about the module's pages, workflows, API endpoints, database schema, field specifications, UI interaction patterns, and validation rules.

Purpose

This MCP is designed to be consumed by AI agents (e.g., Playwright automation, test generation, code review) that need to understand the Technician Portal's behavior without making live API calls. All data is hardcoded from research documents — no credentials, no live connections.

What's Covered

MCP Tools

Setup

npm install
npm run build
npm start

Module Context

• Application: FleetFocus FA/EAM InfoCenter

• Module Path: InfoCenterBase/InfoCenter/ClientApp/src/app/modules/technician/

• Design System: CCL (Component Class Library)

• License: Independent beta license key

• Version: 26.1 Beta (as of research date)

• Legacy Screen ID: 7003 (ASP.NET WebForms predecessor)

Architecture

The Technician Portal uses two API layers:

1. Custom InfoCenter Web API (/Infocenter/api/Technician/...) — Session-cookie auth, business logic operations

2. V2 OData API (:9001/api/v2/...) — OAuth2 Bearer token, entity read/query operations

There are no V3 technician-specific endpoints. All business logic lives in FA-Suite controllers.

Provenance Tracking

Every piece of data in this MCP is tracked back to its source. The provenance registry (src/data/provenance.ts) maps each data path to one or more sources with:

• Source type: jira, github, figma, api, confluence, or manual

• URL: Direct link to the source material

• Description: What information was extracted from the source

• lastChecked: When the source was last verified

• lastChanged: When the source was last observed to have changed

Checking for Updates

Run the source checker to see if any sources have been updated since last check:

# Set credentials
export JIRA_EMAIL="your-email@example.com"
export JIRA_API_TOKEN="your-jira-api-token"
export GITHUB_TOKEN="your-github-pat"

# Run check
npm run check-sources

Or use the shell wrapper:

./scripts/update-sources.sh

The checker:

• Queries Jira REST API for issue updated timestamps

• Queries GitHub API for file last-commit dates

• Compares against recorded lastChanged dates

• Reports which sources have newer changes

• Does NOT auto-apply changes (manual review required)

Exit codes:

• 0 — All sources up to date

• 1 — Changes detected (review needed)

• 2 — Script error

Using Provenance via MCP

Tool: check_provenance
Input: { "data_path": "pages.home" }

Returns the provenance entries showing where the home page data was sourced from and when it was last verified.

Test Fixtures

The test fixture registry (src/data/test-fixtures.ts) provides stable test data values for automation. Fixtures include:

Using Fixtures via MCP

Tool: get_test_fixtures
Input: { "entity": "Equipment" }

Returns all equipment fixtures. Or get a specific fixture:

Tool: get_test_fixtures
Input: { "id": "default_technician" }