Skip to main content
Glama
Sign In
business-central-mcp

business-central-mcp

by SShadowS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to business-central-mcp

No user-submitted related servers found.

    Related Servers

    • business-central-mcp

      EdwardHayes91
      A
      license
      A
      quality
      D
      maintenance
      Gives AI assistants direct access to Microsoft Dynamics 365 Business Central via the native WebSocket protocol, replacing OData, APIs, and browser automation. Enables page navigation, data reading/writing, actions, searches, and report execution.
      14
      1,125 npm
      MIT

    • business-central-mcp

      masoniqbal777
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that gives AI assistants direct access to Microsoft Dynamics 365 Business Central via its native WebSocket protocol, enabling page operations, data reading/writing, actions, search, reports, and more.
      1,125 npm
      MIT

    • business-central-mcp

      keithdev21
      A
      license
      A
      quality
      D
      maintenance
      MCP server that provides AI assistants direct access to Microsoft Dynamics 365 Business Central using its native WebSocket protocol, enabling page navigation, data operations, actions, and report execution without OData or browser automation.
      14
      1,125 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Descriptions are unusually explicit about boundaries, with each tool stating when NOT to use it and pointing at the correct alternative (page reads vs bc_query vs bc_api_list vs bc_data_query, bc_lookup vs bc_navigate, bc_write_data vs bc_execute_action). The remaining soft spot is the read surface: standard entities are reachable via both bc_query and bc_api_list, and bc_data_query can also touch API-exposed tables, so an agent has three plausible entry points distinguished mainly by prose rather than by name.

    Naming Consistency4/5

    Consistent lowercase snake_case with a uniform bc_ prefix and verb-first names (bc_read_data, bc_open_page, bc_execute_action, bc_search_pages). Sub-namespaces (bc_data_*, bc_api_*) follow internal patterns, but the 'data' word is overloaded — bc_read_data/bc_write_data are page operations while bc_data_* are AL table queries — a minor naming wrinkle despite overall predictability.

    Tool Count3/5

    25 tools sits at the heavy end of the scale; the scope genuinely spans four distinct access modes (UI WebSocket pages, Standard API OData, BC 29 native API/data-query MCP tools, AL test runner), which explains but does not shrink the surface. An agent must choose among many entry points before doing anything, making the set borderline heavy.

    Completeness4/5

    Coverage is exceptional across the full workflow lifecycle: discovery (pages, tables, APIs), reads at three levels, writes, actions, dialogs, wizards, file upload/download, reports, company switching, and operation replay/read-back for doubted calls. The notable gap is that bc_search_pages returns AL names but the caller still needs a numeric page ID to open a page, an admitted dead end that forces guesswork.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Resources