Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@FA-Technician-Brain-MCP show me the clock in workflow"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
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.
Related MCP server: mcp-servicefusion
Domain | Coverage |
Pages | 18 screens/pages with full field specs, actions, and navigation |
Workflows | 8 named workflow recipes (clock in, job on/off, create WO, finish/close, etc.) |
API Endpoints | 50+ endpoints across Custom Web API, V2 OData, and V3 |
Database | 23 tables with columns and relationships |
Fields | Component-level specs (type, validation, API mapping) |
Interactions | UI patterns (CCL components, dialogs, drawers, cards) |
Validation | Server-side rules and client-side guards |
Transitions | Work order status state machine |
Permissions | Role/persona-based access by state |
Tool | Description |
| Full page specification by page_id |
| Named workflow recipe with step-by-step instructions |
| Endpoint spec by entity + operation |
| Database table definition with columns |
| Field-level spec (component, validation, API mapping) |
| UI component interaction pattern |
| Validation rules for entity/operation |
| Status transitions from a given state |
| What a persona can do at a given WO state |
| Full-text search across all data |
| Get test fixture data by entity or ID for automation |
| Get provenance info for a data path (sources, last checked dates) |
npm install
npm run build
npm startApplication: 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)
The Technician Portal uses two API layers:
Custom InfoCenter Web API (/Infocenter/api/Technician/...) — Session-cookie auth, business logic operations
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.
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
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-sourcesOr use the shell wrapper:
./scripts/update-sources.shThe 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
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.
The test fixture registry (src/data/test-fixtures.ts) provides stable test data values for automation. Fixtures include:
ID | Entity | Description |
| Operator | CA user with full admin access |
| Equipment | QA-FLEET-001 vehicle |
| Equipment | QA-FLEET-004 (preferred for OM) |
| Vendor | QA test vendor for outsourced maintenance |
| TaskCode | 001-CA-RP-01 task for OM tickets |
| WorkOrder | Template for OPEN WO creation |
| TimeCode | REG time code for clock-in |
| TimeCode | IND time code for indirect labor |
| Location | Main shop location |
| DelayCode | PARTS delay reason |
| Operator | Playwright automation OM user |
| Environment | QADEPLOY URLs and connection info |
Tool: get_test_fixtures
Input: { "entity": "Equipment" }Returns all equipment fixtures. Or get a specific fixture:
Tool: get_test_fixtures
Input: { "id": "default_technician" }Get provenance info for a data path — shows where the data came from and when sources were last checked.
Inputs: data_path (required).
Get API endpoint specification by entity and operation.
Inputs: entity (required), operation.
Get field-level specification including component type, validation, and API mapping.
Inputs: field_id (required).
Get UI component interaction pattern for automation.
Inputs: pattern_id (required).
Get full page specification by page_id. Returns fields, actions, sections, navigation context.
Inputs: page_id (required).
Get what a persona/role can do at a given work order state.
Inputs: persona (required), state.
Get database table definition with columns and relationships.
Inputs: table_name (required).
Get test fixture data for automation. Filter by entity type or retrieve a specific fixture by ID.
Inputs: id, entity.
Get valid status transitions from a given work order state.
Inputs: from_state (required).
Get validation rules for an entity or operation.
Inputs: entity (required).
Get a named workflow recipe with step-by-step instructions for automation.
Inputs: workflow_id (required).
Full-text search across all data (pages, workflows, endpoints, fields, tables, etc.).
Inputs: query (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 12 tools
Each tool targets a distinctly different resource type (endpoints, tables, fields, pages, workflows, validations, transitions, permissions, fixtures, provenance, search). The purposes are largely clear and separable. Minor potential confusion exists between get_api_endpoint, get_table_schema, and get_field since all are spec-lookup tools on different entity types, but their descriptions clearly distinguish target resources.
All 12 tools follow a clean, consistent get_/[search/check] pattern. Nine use the get_ prefix, one uses search_, and one uses check_, all of which are read-only retrieval verbs that fit a coherent convention. Nouns are consistently descriptive (api_endpoint, table_schema, validation_rules, transitions, persona_permissions).
12 tools is within the well-scoped ideal range for a domain knowledge/spec server. Each tool maps to a distinct class of technical reference data that an automation agent might need. This is a slightly-close-but-appropriate count for a comprehensive technical designer/technician knowledge base.
The surface covers a broad range of queryable knowledge: specs, schemas, fields, pages, workflows, validations, transitions, permissions, search, fixtures, and provenance. Minor gaps include the absence of any mutation or comparison tooling (e.g., diff between environments) and no explicit tool for fetching environment/tenant configuration, but core lookup coverage is strong for the stated knowledge-base purpose.
Read-only UteamUP CMMS connector for finding assets and work orders and viewing asset details through five tools. Sign in with OAuth; access follows your company permissions.
Manage tickets, run agents and workflows, query tables, and search workspace knowledge.
Read UpKeep work orders, assets, parts and meters; create requests and work orders.
Tailor Platform for AI assistants: search, list and read the platform documentation.
