Skip to main content
Glama
bersimao

b1-mcp-server for SAP B1

Related Servers

Alternatives to b1-mcp-server for SAP B1

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover SAP B1 entities, inspect their schemas, and perform authenticated CRUD operations through natural language, translating requests into Service Layer API calls.
      208 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with SAP Business One via Service Layer REST API to retrieve and create business data such as partners, orders, invoices, items, and stock levels through natural language.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to read and query SAP OData services and SAP Business One Service Layer data such as business partners, products, items, sales and purchase orders, and invoices, plus gated creation and updates. Writes are disabled by default, support dry-run payload preview, and are verified by an independent read-back, with credentials kept out of tool arguments and local mocks allowing the whole stack to be exercised without a SAP account.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to SAP Business One ServiceLayer, enabling discovery and query of OData entities, service methods, and safe read-only operations by default, with optional write access and simple npx execution.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A reference implementation for connecting SAP Business One to MCP-compatible AI clients, enabling read-only SQL analysis and guarded write workflows.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects SAP Business One to Claude, ChatGPT, and Copilot, providing 12 MCP tools to read business partners, items, sales orders, invoices, quotations, and delivery notes, and to create sales orders.
      AGPL 3.0

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Read vs write tools are clearly separated (execute_service_layer vs execute_service_layer_write), and execute_sql/check_connection/get_schema_info target distinct concerns. The only real ambiguity is between execute_service_layer_write and execute_service_layer_write_unattended, which perform the identical operation and differ only in approval mode; the descriptions explain the distinction but an agent can still easily misselect.

    Naming Consistency5/5

    All tools use snake_case with a consistent verb_noun pattern (execute_*, connect_*, check_*, get_*). The write/write_unattended pair follows a predictable suffix convention rather than breaking the pattern. Names are readable and self-describing throughout.

    Tool Count5/5

    Seven tools is well-scoped for a DB/SAP integration server: connection management, status, schema introspection, read/write SQL, and read/write Service Layer. Each tool earns its place with no obvious filler or redundancy.

    Completeness4/5

    The surface covers connection lifecycle, schema exploration, status checks, and both read and write paths across SQL and Service Layer. The main intentional gap is direct SQL writes (blocked by design, handed to the user), and there is no explicit disconnect tool, but core workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues