Skip to main content
Glama

Related Servers

Alternatives to D365 F&O MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and analyze Microsoft Dynamics 365 Finance & Operations artifacts, read local source code, and generate context-aware solutions through natural language.
      12
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      36 npm
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes 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.
      49
      245 PyPI
      41
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      38 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables D365 F\&O development including object creation, modification, deletion, and analysis through the MCP standard.
      42
      MIT

    TDQS

    A3.8/5.0

    Scored across 20 tools

    Disambiguation3/5

    Descriptions are exceptionally detailed and explicitly cross-reference each other, but there is real overlap among the code-generation/analysis cluster (generate_object, d365fo_file create, object_patterns scaffold, analyze_code, prepare, get_knowledge) and between validation tools (validate_code, run_bp_check) and verification tools (verify_d365fo_project, build_d365fo_project). Many tools are also multi-mode, so an agent must read long descriptions to pick correctly. The guidance helps, but boundaries are not self-evident.

    Naming Consistency3/5

    Most names are snake_case and readable, but the convention is mixed: verb_noun tools (generate_object, get_object_info, find_references, validate_code, build_d365fo_project) coexist with bare nouns (labels, search, object_patterns, security_info, extension_info, d365fo_file) and a bare verb (prepare). d365fo_file additionally hides its action behind a parameter rather than a verb. Still parseable, but not a predictable pattern.

    Tool Count3/5

    At 20 tools the surface is heavy for a single MCP server, even for a large domain like D365FO development. Most tools are justified by distinct lifecycle stages (workspace, search, generate, write, validate, build, test, verify), but the multi-mode design means several tools carry many responsibilities that could have been split or consolidated. It sits in the borderline 16–25 range.

    Completeness4/5

    Coverage is broad: workspace discovery, object search/metadata, pattern and code generation, file CRUD with undo, validation, best-practices, build, unit tests, references, security, extensibility analysis, naming validation, symbol indexing, and knowledge lookup. Minor gaps remain around deployment/package publishing, data management (import/export, DMF), and environment lifecycle operations, but core development workflows are well covered.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data