Skip to main content
Glama
steventswu

YotoMCP Local

by steventswu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to YotoMCP Local

No user-submitted related servers found.

    Related Servers

    • mcp-yoto

      danpillay87
      F
      license
      Not graded
      quality
      A
      maintenance
      Connects a Yoto library to Claude and ChatGPT so parents can browse and build MYO cards, add tracks, set pixel-art icons, and check player status through natural language. It handles Yoto sign-in via OAuth and stores tokens encrypted so nothing readable is retained.
      -

    • cf-control-mcp

      nimazasinich
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables inspecting and managing a Cloudflare account from MCP-compatible clients, with OAuth/PKCE support and a read-only mode for ChatGPT, plus a legacy bearer-token path for full tool access.
      -

    • bytebase-mcp

      ahmedbally
      A
      license
      A
      quality
      B
      maintenance
      Enables SQL querying, schema browsing, query history, and human-approved change-plan workflows against Bytebase via the Connect-RPC API, secured with OAuth 2.1 PKCE and multi-process-safe token rotation.
      14
      18 npm
      1
      MIT

    • xero-mcp-auth

      JoshAntBrown
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables free Xero accounting access through MCP clients by handling one-time PKCE sign-in and refresh-token persistence, letting users run the official Xero MCP server without a paid Custom Connection.
      10 npm
      MIT

    • jwx-mcp

      JustworxCloud
      F
      license
      A
      quality
      C
      maintenance
      Exposes Justworx devices to AI agents as MCP tools and resources, backed by the public Developer API. Supports local stdio and hosted remote OAuth operation for controlling device IO, rules, and viewing live state.
      6
      -
    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.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: auth workflow steps are separate, card operations are get vs list, device listing is unique, and logout is standalone. No two tools could be confused.

    Naming Consistency4/5

    All tools use snake_case with a yoto_ prefix, but the auth tools vary in structure (auth_status, auth_complete, auth_start) while others follow verb_noun (get_card, list_cards, list_devices). Minor deviation from a uniform verb_noun pattern.

    Tool Count5/5

    Seven tools are well-scoped for a local Yoto integration focused on authentication and read-only access. Each tool earns its place without redundancy.

    Completeness4/5

    The auth lifecycle (start, complete, status, logout) is fully covered, and read operations for MYO cards and devices are present. Minor gaps include no search/filter for cards and no detailed device inspection, but the core read-only scope is well served.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources