Skip to main content
Glama
Sign In
BAND MCP

BAND MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to BAND MCP

No user-submitted related servers found.

    Related Servers

    • TeamSnap MCP Server

      mrelph
      A
      license
      A
      quality
      D
      maintenance
      Connects Claude to TeamSnap accounts to access teams, rosters, events, and availability data. Supports OAuth 2.0 authentication with optional AWS serverless deployment for permanent HTTPS callback URLs.
      9
      5
      MIT

    • meta-mcp

      alissonjcdev
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to Instagram through Meta's official API, enabling users to retrieve account insights, analyze professional profiles, publish photos/carousels/reels/stories, manage comments, read and respond to Direct messages, and call any Graph API endpoint.
      36 npm
      MIT

    • garmin-mcp

      alyssindewonderland
      A
      license
      B
      quality
      B
      maintenance
      Connects Claude to a personal Garmin Connect account so users can ask natural-language questions about sleep, HRV, body battery, stress, heart rate, training readiness and activities, and optionally create or schedule workouts and log weigh-ins. Reads are returned as trimmed summaries with optional full JSON, and writes stay disabled unless explicitly enabled.
      24
      MIT

    • Daash

      Bartolome69
      A
      license
      A
      quality
      B
      maintenance
      Daash connects Garmin Connect to ChatGPT and Claude. Your assistant reads your runs, splits, sleep, HRV, Body Battery and recovery, and writes structured workouts and whole training plans to your Garmin calendar, so they're on your watch at the next sync. Free, hosted, open source. Works on free Claude.
      26
      4
      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.9/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: overview counts (whats_new), keyword search, feed paging, pinned notices, single-post read, comments, events, chats, and two writes are all clearly separated by their descriptions. The only mild overlap is that band_get_post returns comments by default while band_list_comments exists for paging, but the descriptions make the intended split explicit. band_healthcheck is a clearly separate diagnostic, not confusable with data tools.

    Naming Consistency4/5

    All tools share a uniform band_ prefix and snake_case, with a consistent verb_noun pattern for the bulk of them (list_*, get_*, search_*, create_*). The two exceptions, band_whats_new and band_healthcheck, break the verb_noun pattern but remain unambiguous and readable. No style mixing (camelCase, inconsistent verb forms) is present.

    Tool Count4/5

    16 tools is slightly on the heavy side but each covers a genuinely different BAND object (bands, members, posts, comments, notices, events, chats) plus writes and a diagnostic, so nothing feels redundant. A consolidation of get/list pairs for events and chats could trim it, but the scope justifies the count.

    Completeness3/5

    Read coverage is strong across bands, members, posts, comments, notices, events, and chats, but the surface is write-thin: no update or delete for posts and comments, no event creation/RSVP, and no way to send a chat message (history explicitly unavailable). Agents can read almost anything but cannot correct or remove content they create, which is a notable lifecycle gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources