xpp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XPP_MCP_CONFIG | No | Path to the optional config file. Leave out for read-only defaults. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reference_treeC | Inspect the reference tree by package, model, artifact type, artifact, and member. |
| reference_resolveC | Resolve an artifact or member by canonical ID or case-insensitive name. |
| reference_referencesA | Read bounded incoming or outgoing typed reference edges for an artifact or member, from the IDE's cross-reference store. An artifact id (/Tables/CustTable) covers every nested member (fields, methods, field groups, form data sources and controls...), its extensions (CustTable.) and metadata links such as menu item -> form, security privilege -> menu item, query/entity/form field bindings and EDT relations (provider ide-xref-metadata, paths dynamics://Type/Name/...?Property). A member id (/Tables/CustTable/Fields/AccountNum, /Forms/F/DataSources/D/DataFields/F, /Forms/F/Controls/C) narrows to that member. Label targets carry their en-US text. Empty results can mean the cross-reference data was never built for the referencing model: run reference_reindex on it and retry. |
| reference_impactC | Traverse bounded incoming dependents or outgoing dependencies at artifact granularity. |
| reference_extensionsA | List what extends an artifact: its extension elements (TableExtension, FormExtension, EnumExtension... named .), chain-of-command classes ([ExtensionOf]), event handlers ([DataEventHandler], [FormEventHandler], [FormDataSourceEventHandler], [FormControlEventHandler], [FormDataFieldEventHandler], [PreHandlerFor], [PostHandlerFor]) and delegate subscribers ([SubscribesTo]) that name the artifact or one of its members. Use it before changing an artifact to see the code that hooks into it. |
| reference_labelsA | Resolve label ids (@File:LabelId, or legacy @SYS12345) to their text in one language, from the label files Visual Studio knows. text is null when the label file or label is not found (Microsoft label files shipped only as binaries are not readable). |
| reference_graphA | Build a dependency graph between classes from the IDE's cross-reference store: starting from root classes, follow outgoing dependencies or incoming dependents up to a depth. Edges are folded to artifact level and list the methods/members involved; edges between different modules are flagged and summarized as boundaries. Only classes are expanded further; tables, EDTs, enums and others appear as leaves. |
| reference_refreshA | Drop the cached project-membership data so the next reference query reads Visual Studio again. |
| reference_statusA | Read the freshness and provenance of the reference data (live from Visual Studio). |
| source_readB | Read a bounded .xml or .xpp source file with its encoding, newline style, and SHA-256. |
| source_parseB | Parse Dynamics XML or X++ source and return artifact members, source references, and diagnostics. |
| source_validateB | Validate XML well-formedness, Dynamics artifact identity, and lexical X++ structure. |
| source_writeA | Dry-run or atomically replace an existing source file after validation, preserving encoding and newlines. |
| project_inspectB | Parse and validate an .rnrproj, including artifact membership against the reference index. |
| solution_inspectB | Enumerate and validate X++ and other projects in a Visual Studio .sln file. |
| project_updateC | Dry-run or create/update an .rnrproj with reconciled artifacts and optional solution registration. |
| solution_updateC | Dry-run or add, remove, or reorder X++ projects with dependency and configuration reconciliation. |
| artifact_registryB | List all fixture-backed artifact metadata and explicitly unavailable types. |
| artifact_designC | Generate a minimal fixture-shaped XML design without reading or writing files. |
| artifact_validateB | Validate a supported artifact's XML, X++, registry shape, identity, filename, and companion metadata. |
| artifact_buildB | Dry-run or create artifact XML and any label/resource payload, reconcile optional project membership; this does not compile X++. |
| artifact_updateB | Dry-run or validate and update/rename artifact XML and any companion payload, reconciling indexed project memberships in one transaction. |
| artifact_removeA | Dry-run or remove artifact XML, any companion payload, and indexed project memberships after impact analysis; actual removal requires confirm=true. |
| build_projectB | Dry-run or compile an X++ .rnrproj in the open Visual Studio. |
| build_solutionB | Dry-run or compile the X++ projects of the solution open in Visual Studio. |
| build_modelB | Dry-run or compile a Dynamics 365 model in the open Visual Studio (Dynamics 365 > Build Models) and bounded logs. |
| reference_reindexA | Rebuild the Visual Studio cross-reference data for a model (cross-reference-only model build, no compile). Use it when reference_references/reference_impact/reference_graph return nothing for code you know exists, e.g. fields or methods added in an extension model: reindex the model that holds the referencing code, then query again. Needs policies.allowBuilds. |
| ide_solution_projectsA | List the projects (and their models) of the solution open in Visual Studio, as the IDE sees them. |
| ide_project_itemsB | List the elements of a project as the IDE sees them, optionally filtered by artifact type such as Class, Table, Form or Edt. |
| ide_referencesB | Find references to an element using the live cross-reference store of the open Visual Studio (not a stale archive). Targets use cross-reference paths such as /Classes/Name, /Classes/Name/Methods/method or /Tables/Name. |
| ide_definitionB | Resolve where an element is defined according to the open Visual Studio: every model that defines it (with layer and module) and the element file in each. |
| ide_searchA | Search the artifact names of one AOT element type (Class, Table, Form, MenuItemDisplay, SecurityRole, DataEntityView, Service, ...: the Application Explorer node type) across the models visible to the loaded solution, including Microsoft dependency models, using the IDE's metadata. pattern is a case-insensitive regular expression; omit it to list names. |
| ide_type_relationsB | Class relationships from the open Visual Studio: bases (inheritance chain), derived (classes extending it), implementers (classes implementing an interface) or attributed (classes carrying an attribute). |
| environment_infoA | Describe the Dataverse / online Finance and Operations environment Visual Studio is connected to (URLs, type, versions, tenant, busy flag). If Visual Studio is not connected it opens its connection wizard, so this refuses unless allowPrompt is true or a connected environment was already seen in this session. No access token is ever returned. |
| environment_connectA | Start Visual Studio's own Connect to Dataverse command and wait for the user to complete the interactive sign-in and solution selection in Visual Studio, then describe the connected environment. The sign-in itself cannot be automated. |
| db_syncA | Dry-run or run a full database synchronization through Visual Studio. Always runs preflight checks. A local runtime syncs only databaseSync.target (confirmDatabase must equal its database name). A CloudRuntime environment syncs only databaseSync.finOpsUri, which must be the environment Visual Studio is connected to (confirmEnvironment must equal its host); it needs databaseSync.allowCloudRuntime and a connection confirmed this session, and never opens a connection wizard. A real run also needs policies.allowDatabaseSynchronization and dryRun=false. The online sync reports no result of its own, so the extension watches the Power Platform output for the Dataverse async operation status (30 succeeded, 31 failed, 32 canceled); success is null if none appears before timeoutMs. |
| server_statusA | Read server version, safety policies, and configured resource counts. |
| resolve_pathC | Resolve an existing file or directory visible to the solution loaded in Visual Studio. |
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 38 tools
Prefix grouping helps, but several tools target nearly the same question through different backends: reference_references vs ide_references (both find references), reference_impact vs reference_graph vs ide_type_relations (all dependency traversal), and solution_inspect vs ide_solution_projects vs project_inspect vs ide_project_items (project/solution enumeration). The descriptions do explain the distinction (cached xref store vs live IDE, artifact vs class granularity), so an attentive agent can pick, but the boundaries require careful reading.
Clear domain prefixes (reference_, source_, project_, solution_, artifact_, build_, ide_, environment_, db_) followed by verb or noun, mostly verb_noun (source_parse, artifact_validate, build_model). A few noun-only outliers (reference_tree, artifact_registry, environment_info) and the mix of project_/solution_/ide_ prefixes for overlapping concepts are minor deviations rather than a breakdown.
38 tools is well past the 25-tool threshold and a handful are near-redundant or thin utility calls (reference_refresh, reference_status, server_status, resolve_path, artifact_registry) that inflate the surface. The domain is genuinely broad (xref, IDE, source, project, artifact, build, environment, DB), but the set could be consolidated meaningfully.
Coverage is strong: read/parse/validate/write for sources, design/build/update/remove for artifacts, inspect/update for projects and solutions, three build scopes, cross-reference querying and reindexing, plus environment and DB sync. Minor gaps remain — no delete/rename for projects or solutions, no test execution or rollback, and no explicit 'list artifacts in project' beyond ide_project_items.