Skip to main content
Glama
ackbarguppi-ai

Thinkific MCP Server

by ackbarguppi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Thinkific MCP Server

No user-submitted related servers found.

    Related Servers

    • Shopmonkey MCP Server

      AbbottDevelopments
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to interact with the Shopmonkey REST API to manage shop management data including work orders, customers, vehicles, and inventory. It provides 33 tools across 9 resource groups with built-in support for rate limiting, concurrency control, and multi-location management.
      69
      2
      MIT

    • Autotask MCP Server

      TICnine
      A
      license
      C
      quality
      C
      maintenance
      Provides AI assistants with direct access to Autotask PSA for MSP operations. Enables natural language interaction for ticket management, time logging, company lookups, project tracking, and billing review through 39 comprehensive tools.
      100
      19 npm
      Apache 2.0

    • mcp-appstore-connect

      ahmetsina
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.
      61
      32 npm
      11
      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

    C2.7/5.0

    Scored across 109 tools

    Disambiguation2/5

    Many tools overlap: gql_* tools duplicate REST equivalents (get_product vs gql_product, get_bundle vs gql_bundle), and there are multiple membership tools (add_user_to_group, create_enrollment, create_bundle_enrollment) whose boundaries are unclear. Promotion/coupon creation is also easy to confuse.

    Naming Consistency3/5

    Most REST tools follow a consistent verb_noun pattern (create_, list_, get_, update_, delete_). However, the 20 GraphQL tools use a separate gql_ prefix with varying verbs (gql_community, gql_create_post, gql_bulk_add_users_to_groups), creating two naming conventions. Within each group, naming is fairly predictable.

    Tool Count2/5

    109 tools is excessive and will overwhelm agents. While the domain is broad, many tools are redundant (gql_* duplicates REST endpoints) and could be consolidated or removed. The sheer count makes selection and discovery difficult.

    Completeness3/5

    The surface covers CRUD for many entities (users, categories, coupons, groups, instructors) and community operations via GraphQL. However, core educational workflows are incomplete: there are no create/update/delete operations for courses, chapters, contents, or bundles, and no review moderation tools. This is a notable gap given the platform's purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources