xpp-mcp
Related Servers
Alternatives to xpp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Dynamics 365 Finance & Operations developers to search, retrieve, and analyze X++ code across a large indexed codebase, with tools for impact analysis, extensions, references, and best-practice validation.49 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to ground on real D365 F&O AOT metadata locally and offline, preventing hallucinated X++ field names and Chain of Command signatures.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and analyze Microsoft Dynamics 365 Finance & Operations artifacts, read local source code, and generate context-aware solutions through natural language.71 npm12-
- AlicenseAqualityAmaintenanceEnables AI-assisted X++ development for Dynamics 365 Finance and Operations by pre-indexing the entire codebase and providing 54 specialized tools for metadata lookup, code generation, and best practice validation.20459 npm173MIT
- AlicenseNot gradedqualityDmaintenanceEnables D365 F\&O development including object creation, modification, deletion, and analysis through the MCP standard.42MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only analysis of Dynamics 365 F&O Electronic Reporting exports through MCP tools for linting, structural and binding diffs, three-way rebase checks, export summaries, and inspection.MIT
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.