D365 F&O MCP Server
Related Servers
Alternatives to D365 F&O MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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 gradedqualityBmaintenanceEnables AI assistants to search and analyze Microsoft Dynamics 365 Finance & Operations artifacts, read local source code, and generate context-aware solutions through natural language.137 npm12-
- AlicenseNot gradedqualityBmaintenanceEnables 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.72 npm3MIT
- AlicenseAqualityBmaintenanceExposes the full capabilities of Microsoft Dynamics 365 Finance & Operations to AI assistants through 49 comprehensive tools and standardized protocol interactions. It enables sophisticated workflows including OData operations, metadata discovery, and secure database analysis.4966 PyPI40MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to explore metadata, query data, and perform write operations across multiple Microsoft Dynamics 365 Finance & Operations environments. It features specialized tools for OData execution and data analysis with built-in read-only safety for production environments.84 npm10MIT
- AlicenseNot gradedqualityDmaintenanceEnables D365 F\&O development including object creation, modification, deletion, and analysis through the MCP standard.42MIT
TDQS
Scored across 20 tools
Most tools target distinct resources/actions, and the descriptions actively disambiguate (e.g. 'use X instead of Y', 'already folded into...'). However, genuine overlaps exist: `prepare` deliberately duplicates search/get_object_info/analyze_code/generate_object, `d365fo_file(action="generate")` overlaps `generate_object`, and build/run_bp_check/verify_d365fo_project form a pipeline where invocation boundaries must be inferred. These are explained but still create selection risk.
Casing is uniformly snake_case and most names are clear verb_noun (get_object_info, run_bp_check, generate_object, validate_code, find_references). A minority are bare nouns/vague verbs (prepare, search, labels, object_patterns, security_info, extension_info, d365fo_file), which is a minor inconsistency but still readable and predictable.
20 tools is above the ideal 3-15 band and trends heavy, but the domain (D365 F&O code generation, indexing, builds, validation, security, patterns, knowledge) is genuinely broad, so each tool maps to a distinct capability. It sits slightly over-scoped rather than padded.
The surface covers an unusually full authoring lifecycle: context discovery, generation, validation, naming, indexing, labels, build/verify, extensibility analysis, security, and knowledge lookup. Minor gaps remain around deployment/package, data management, and environment operations, but core CRUD/lifecycle workflows for X++/AOT authoring are covered with no obvious dead ends.