Skip to main content
Glama
Influencers-Club

Influencers Club MCP Server

Official
by Influencers-Club
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Influencers Club MCP Server

No user-submitted related servers found.

    Related Servers

    • instagram-mcp

      yeswanthreddyk
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for organic Instagram analytics via the Meta Graph API, providing read-only tools for profiles, media, insights, audience, and optional publishing.
      GPL 3.0

    • mcp-instagram

      michalmalek318-star
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with Instagram Business accounts via the Instagram Graph API, enabling profile retrieval, media publishing, insights, and direct messaging.
      MIT

    • datalikers-mcp

      subzeroid
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for DataLikers — 29 hand-built tools for Instagram & TikTok data: user search by demographics (gender/age/race/country), profiles, engagement, hashtags, locations, business accounts, top-users. Local stdio via npx -y datalikers-mcp, requires only DATALIKERS_KEY.
      16
      8
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources (locations, languages, brands, etc.). The only potential confusion is between discover_creators and discover_creators_to_file, and between enrich_by_handle and enrich_by_handle_raw, but descriptions explicitly clarify the difference with cost and output format.

    Naming Consistency3/5

    The set mixes get_*, discover_*, enrich_*, audience_*, and standalone nouns like connected_socials and check_credits. While each subgroup is internally consistent, the overall pattern is inconsistent, making it harder to predict tool names.

    Tool Count3/5

    22 tools is on the heavy side for the domain, though many are simple filter getters (9 of them) that could be consolidated. The breadth of discovery, enrichment, and export operations justifies the count, but it feels somewhat bloated.

    Completeness3/5

    Core workflows (discover, enrich, posts, overlap, exports) are covered. However, the descriptions reference create_batch_enrichment for bulk enrichment, which is not included in the toolset, creating a clear gap that could cause agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources