Skip to main content
Glama
Sign In
Frame.io V4 MCP

Frame.io V4 MCP

by yong6330
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Frame.io V4 MCP

No user-submitted related servers found.

    Related Servers

    • blazemeter-explorer

      aminamos
      A
      license
      A
      quality
      D
      maintenance
      Enables querying and invoking BlazeMeter's public API v4 explorer operations, including vault settings, session management, and static asset routes.
      3
      MIT

    • HyperFrames MCP Server

      trextrinorex
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables remote management of HyperFrames video projects over Streamable HTTP, including project creation, file authoring, linting, validation, composition inspection, rendering, transcription, TTS, catalog access, documentation, and CLI operations.
      -

    • sf-api-explorer

      nfunky
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables exploring a Salesforce org's REST and Apex REST APIs by generating an OpenAPI catalog, searching sObjects and operations, hydrating field schemas, and exporting OpenAPI documents.
      MIT

    • SandBase MCP

      dKaminski2652
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to discover, inspect, and run 2,000+ AI models and data APIs—including LLMs, image, video, and audio generation—through a single authenticated local bridge with per-call pricing shown before execution. It also supports run status tracking, account balance checks, and rollback from one browser sign-in.
      556,724 npm
      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

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: verify_connection checks OAuth, search_tools discovers operations, get_tool_schema retrieves parameter details, invoke_tool executes an operation, and upload_local_file handles file uploads. No two tools overlap in a way that would cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., verify_connection, search_tools, get_tool_schema, invoke_tool, upload_local_file). There is no mixing of conventions.

    Tool Count5/5

    Five tools are well-scoped for a meta-gateway that wraps the entire Frame.io V4 OpenAPI catalog. Each tool earns its place, and the count avoids both bloat and thinness.

    Completeness5/5

    The server provides full access to the Frame.io V4 API through search_tools, get_tool_schema, and invoke_tool, plus a specialized upload tool and an OAuth check. No obvious gaps exist for its stated purpose as a dynamic API gateway.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources