Skip to main content
Glama
rustam-zarifov

mto-mcp-server

by rustam-zarifov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mto-mcp-server

No user-submitted related servers found.

    Related Servers

    • inventory-doctor

      shidesheng0218
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to diff inventory snapshots from CSV files or live Shopify stores, surfacing SKU mismatches, oversell risks, blank-vs-zero issues, barcode conflicts, and sync health, with data processed locally.
      MIT

    • open-jobsite

      raoulstongea
      A
      license
      A
      quality
      B
      maintenance
      Enables construction teams to create local projects, record sourced field evidence, run deterministic quantity calculations, and draft daily logs, estimates, and change orders with visible assumptions and human approval gates. Keeps all data local and portable with no external side effects.
      10
      Apache 2.0
    • csvbox-mcp-server by csvbox-io

      csvbox-mcp-serverofficial

      csvbox-io
      A
      license
      A
      quality
      B
      maintenance
      Enables managing CSVBox importer sheets through MCP tools, including creating, replacing, patching, generating, validating, and scaffolding importers from any MCP-compatible client.
      9
      36 npm
      MIT

    • sheetspec

      helloo1568
      A
      license
      Not graded
      quality
      A
      maintenance
      Validates Excel (.xlsx) workbooks against reviewed, lockable acceptance contracts, catching errors and outputting structured issues that agents can repair.
      1
      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.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: diff_mto_scsa is explicitly read-only comparison, while apply_mto_update is write-back with dry-run and removal safeguards. There is no realistic ambiguity about which tool to select for a given task.

    Naming Consistency5/5

    Both names follow a consistent verb_noun snake_case pattern: diff_mto_scsa and apply_mto_update. The shared 'mto' prefix ties them to the same domain, and the verbs clearly signal read vs. write actions.

    Tool Count4/5

    Two tools is slightly below the typical 3-15 range, but this is a deliberately narrow reconciliation workflow where diff and apply are exactly the needed operations. The small count is reasonable and neither tool is redundant.

    Completeness5/5

    The server covers the full diff-then-apply lifecycle: it can identify mismatches, removed items, and new items, and then safely write corrections back, including controlled removal handling. Parametrized categories, dry-run preview, and output_path prevent dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources