UI Journey MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_flowsB | List mapped flows and available exact revisions. Mapping alone is not execution evidence. |
| get_flowC | Get the mapped states, transitions and source dependencies of a flow. |
| get_flow_evidenceB | Read stored flow evidence, screenshots and failures. Does not run a browser. Supply an exact revision when multiple versions exist. |
| compare_flowB | Compare contracts and evidence for two exact revisions. This is a structural/status comparison, not an aesthetic image verdict. |
| trace_journeyB | Find a shortest declared interaction path within a mapped flow. A path is not proof it passed. |
| get_ui_impactB | Find mapped flows whose declared entry files or recorded dependency closures intersect changed files. Unknown coverage remains possible. |
| get_coverage_gapsC | List unverified or failed mapped states/transitions for one flow. Does not claim exhaustive application coverage. |
| get_change_evidenceB | Find stored runs associated with a PR number and optionally an exact revision. PR metadata is supplied by the importer, not authenticated by this server. |
| get_evidence_imageA | Return a stored PNG inline for a project and content hash obtained from get_flow_evidence. Never fetches arbitrary URLs or paths. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a fairly distinct purpose: listing, fetching metadata, fetching evidence, comparing revisions, tracing paths, and finding impact/coverage gaps. Some overlap exists between get_flow_evidence and get_change_evidence, and between get_ui_impact and get_coverage_gaps, but descriptions clarify retrieval vs. discovery and revision vs. PR context.
All nine tools follow a consistent snake_case verb_noun pattern (list_flows, get_flow, compare_flow, trace_journey, get_evidence_image), with no mixed casing or verb styles.
Nine tools is a well-scoped set for a UI journey/evidence server, covering discovery, inspection, comparison, tracing, and impact analysis without bloat.
The surface covers the lifecycle of mapping, retrieving, comparing, tracing, and gap analysis, but lacks explicit create/update/delete operations for flows or mappings, so agents cannot mutate mappings through this server.