Skip to main content
Glama
joanbosch

exact-synergy-globe-mcp

by joanbosch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to exact-synergy-globe-mcp

No user-submitted related servers found.

    Related Servers

    • odatav4-mcp

      singlebarrel
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for OData v4 endpoints, especially Microsoft Dataverse/Dynamics 365, enabling authentication, schema discovery, querying, CRUD, and more via natural language.
      -

    • dataverse-mcp-server

      rededis
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Microsoft Dataverse API with safe-by-default configuration. Works with any Dataverse / Dynamics 365 environment.
      23
      36 npm
      8
      MIT

    • Exact Online

      iwebdevnl
      A
      license
      Not graded
      quality
      C
      maintenance
      Hosted MCP server for Exact Online. Ask questions, pull reports, and prepare bookings you approve first.
      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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool addresses a distinct layer: connection/capabilities, entity and action catalogs, schema discovery, and record reads. The overlap between list_entities and list_entity_records is clarified by 'metadata entities' versus 'entity records', so selection should be unambiguous.

    Naming Consistency5/5

    All tools share the 'exact_' prefix and use a consistent verb-noun scheme: get_ for single objects/schemas/info and list_ for catalogs. There is no mix of verb styles or casing.

    Tool Count5/5

    Eight tools is a well-scoped size for an Exact integration. Each tool covers a distinct need without redundant or trivial additions.

    Completeness4/5

    The read-side surface is complete: server health, capabilities, entity/action discovery, schemas, single-record reads, and filtered list reads are all present. The only notable gap is that action schemas can be inspected but there is no execute_action tool to invoke discovered actions, leaving a potential dead end for action workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources