Skip to main content
Glama
Sign In
SensorForge MCP Server

SensorForge MCP Server

by sidupreti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SensorForge MCP Server

No user-submitted related servers found.

    Related Servers

    • edge-forge-mcp

      eduplopez
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to export PyTorch models to validated ONNX, quantize them to FP16 or INT8, measure fidelity drift and benchmark latency and memory against edge hardware budgets. It also autonomously searches export and precision configurations and persists JSON, Markdown and HTML reports.
      MIT
    • chronosml-mcp

      chronosml-mcpofficial

      kardashevproject
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to estimate wall-clock runtime, peak memory footprint, OOM risk, and optimal batching before launching ML training or inference jobs, and to log completed runs for continuous calibration. It exposes just two ultra-compact tools so estimation fits in under 200 tokens of agent context.
      Apache 2.0

    • ]picpress-mcp

      xiaoqiangzaici
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to compress photos on the local machine to an exact target size in B, KB, or MB, with tools for batch compression, pre-flight feasibility estimation, image info lookup, and format listing, all returning structured JSON statuses.
      2
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    The core workflow tools are well separated: check_data validates locally, check_fit measures fit without data, lossless shrinks without data, and optimize retrains on data, with descriptions stating the ordering. The main soft spot is the run-inspection cluster (list_runs, run_status, wait_for_run, get_report) plus download, which overlaps with lossless since lossless also downloads and unpacks output — but each still has a stated distinct behavior.

    Naming Consistency3/5

    Most tools follow snake_case verb_noun (list_runs, stop_run, check_fit, check_data, run_status, wait_for_run, get_report), but a large minority are bare single words of mixed grammatical type: download, optimize (verbs), account (noun), lossless (adjective). Readable, but the convention is not predictable across the set.

    Tool Count5/5

    Twelve tools map cleanly onto a coherent pipeline (inspect chips, validate data, check fit, optimize/lossless, poll, download, report, account, stop) with no filler or duplicate endpoints. Well within the well-scoped 3–15 range.

    Completeness4/5

    The run lifecycle is covered end to end: discovery (list_chips), preflight (check_data, check_fit), execution (optimize, lossless), progress (run_status, wait_for_run), cancellation (stop_run), output retrieval (download, get_report), plus history and quota (list_runs, account). Minor gaps remain, such as deleting/cleaning up old runs or a plain fetch of results without unpacking into a project directory.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources