Skip to main content
Glama
tolatolatop

RunningHub MCP Server

by tolatolatop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to RunningHub MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Video Gen

      the-code-learner
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP server that connects AI clients to local media-generation backends like ComfyUI and Blender, and provides built-in utilities for video/audio analysis, editing, subtitles, speech, and scene detection via a persistent file cache.
      Apache 2.0

    • MCP Server Replicate

      gerred
      A
      license
      C
      quality
      D
      maintenance
      A FastMCP server implementation that facilitates resource-based access to AI model inference, focusing on image generation through the Replicate API, with features like real-time updates, webhook integration, and secure API key management.
      18
      16
      MIT

    • minio_mcp

      ClearMind1
      F
      license
      C
      quality
      D
      maintenance
      A FastMCP-based server that enables uploading text and base64-encoded content to MinIO object storage through an HTTP transport. It supports automated bucket management and secure file path generation to streamline remote storage operations.
      -

    • File Server MCP

      g-linville
      F
      license
      Not graded
      quality
      D
      maintenance
      A hybrid REST + MCP file server for managing files with large file streaming support, enabling AI agents and web frontends to perform file operations via MCP tools and REST APIs.
      -
    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

    Disambiguation3/5

    There is overlap between submit_task and run_task_and_wait (both submit tasks), and between query_task_outputs and run_task_and_wait (both check status/output). However, descriptions clarify the combination pattern in run_task_and_wait, so ambiguity is limited but still present.

    Naming Consistency4/5

    Most tools follow a consistent snake_case verb_noun pattern (e.g., get_node_info, submit_task). The exception is run_task_and_wait, which deviates with 'and_wait', and 'list_tasks' vs 'query_task_outputs' use different verbs for similar operations.

    Tool Count5/5

    8 tools is well-scoped for an AI task runner, covering submission, synchronization, file upload, and status queries without being excessive or minimal.

    Completeness4/5

    Core workflow (submit/run, query output, sync status, upload files) is covered. Missing tools for listing available applications or canceling tasks, but these are not critical for the primary use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources