Skip to main content
Glama
awnt9

mcp-netsuite-practice

by awnt9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-netsuite-practice

No user-submitted related servers found.

    Related Servers

    • dumate-supply-chain-mock-api

      pipiwolve
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides mock APIs and deterministic seed data for ERP/OMS, WMS, and CRM systems, enabling supply chain data exploration and integration testing.
      -

    • netsuite-suiteanalytics-odbc

      samson10504
      A
      license
      B
      quality
      B
      maintenance
      A local, read-only MCP server for querying NetSuite SuiteAnalytics Connect through a user's locally installed ODBC driver, exposing bounded tools for SQL queries, table metadata, and connection status.
      4
      10 npm
      Apache 2.0

    • SupliiChain MCP Sandbox

      AMinerSolution
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight, local inventory-intelligence MCP server that enables querying structured inventory schemas with read-only, zero-config tools for stock levels, velocity metrics, and purchase orders.
      4 npm
      MIT

    • inventory-mcp

      ruanderson1
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for querying product inventory, providing tools to retrieve product details and stock quantities.
      -

    • NetSuite MCP Server

      dsvantien
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server providing access to NetSuite data through OAuth 2.0 with PKCE authentication. Works seamlessly with any MCP-compatible client including Claude Code, Cursor IDE, and Gemini CLI.
      2
      37 npm
      20
      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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target completely distinct domains: inventory (stock levels by SKU) and order fulfillment (order status by ID). There is no overlap in purpose or arguments, so an agent can easily select the correct tool.

    Naming Consistency5/5

    Both tools follow a consistent get_noun_noun pattern (get_stock_level, get_order_status), using snake_case and a clear verb prefix. The naming is predictable and uniform.

    Tool Count3/5

    With only two tools, the server feels minimal. For a practice server this may be intentional, but it borders on too sparse to represent a meaningful integration, though each tool covers a distinct, useful query.

    Completeness2/5

    The tool surface only provides single-record lookups (by SKU and order ID) with no list, create, update, or delete operations. This is a significant gap for an ERP domain like NetSuite, where typical workflows require broader coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources