Skip to main content
Glama
bperkinspdx

yoto-mcp-server

by bperkinspdx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to yoto-mcp-server

No user-submitted related servers found.

    Related Servers

    • YotoMCP Local

      steventswu
      F
      license
      A
      quality
      A
      maintenance
      Enables secure local management of Yoto cards, devices, and audio uploads through the official Yoto API, using OAuth PKCE authentication with read-only tools enabled by default and opt-in writes.
      7
      -

    • OpenCode MCP Gateway

      gjabdelnoor
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes local OpenCode instances as remote MCP servers for Claude and ChatGPT, enabling terminal access, session management, and interactive human-in-the-loop workflows. It simplifies deployment for local machines using Cloudflare Tunnels to provide secure public connectivity and OAuth support.
      -

    • mcp-auth-proxy

      manio143
      F
      license
      Not graded
      quality
      D
      maintenance
      Bridges stdio-based LLM harnesses to OAuth-protected remote MCP servers via Streamable HTTP, handling PKCE browser login and token refresh automatically.
      6 npm
      -

    • remote-control-mcp

      Hexpy-Games
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI services like Claude and Cursor to remotely control a Mac by executing shell commands, managing files, and running AppleScript for UI automation. Access is secured through OAuth 2.0 authentication and encrypted tunnels to protect remote interactions.
      2
      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 6 tools

    Disambiguation4/5

    Each tool targets a distinct action: authentication, checking auth, uploading audio, adding tracks, listing cards, and fetching card details. The only potential confusion is between yoto-auth and yoto-check-auth, but their descriptions clearly differentiate performing authentication versus checking status.

    Naming Consistency4/5

    All tools use a consistent 'yoto-' prefix followed by a verb-noun pattern (e.g., upload-audio, list-cards, get-card). The exception is yoto-auth, which is a single verb, but it still fits the overall style and is readable.

    Tool Count5/5

    Six tools is well-scoped for a Yoto integration server, covering authentication, uploading, track management, and card queries without unnecessary bloat. Each tool serves a clear purpose.

    Completeness4/5

    The tool set covers the core workflow of authenticating, uploading audio to create cards, adding tracks, and querying cards. Minor gaps exist, such as no delete or update card operations, but these are not critical for the primary use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources