Skip to main content
Glama
Sign In
LinkJolt MCP Server

LinkJolt MCP Server

by Efesop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to LinkJolt MCP Server

No user-submitted related servers found.

    Related Servers

    • Refgrow MCP Server

      refgrow
      A
      license
      A
      quality
      C
      maintenance
      MCP server for managing affiliate and referral programs. Track referrals, manage affiliates, process conversions, and handle payouts through AI assistants like Claude, Cursor, and ChatGPT.
      18
      314 npm
      2
      MIT

    • flexoffers-mcp

      juangb87
      F
      license
      A
      quality
      D
      maintenance
      Integrates FlexOffers API v3 as an MCP server, enabling users to manage affiliate programs, list promotions, search products, generate deeplinks, and retrieve payment reports through natural language.
      14
      -

    • FirstPromoter MCP Server

      a-petukhov
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that provides AI assistants with access to the FirstPromoter affiliate management platform for managing referrals, promoters, campaigns, and commissions. It is designed for remote multi-user deployment and supports operations via HTTP/SSE transport.
      -
    • @referalli/mcp

      @referalli/mcpofficial

      Referalli
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients like Claude and Cursor to read referral and affiliate program data—programs, partners, referrals, fraud cases, and ROI—and, after a two-step preview-and-confirm flow, create partners, links, and coupons, approve or void referrals, and draft payout runs. It runs locally over stdio and connects to Referalli using an API key whose scopes limit what the server can do.
      21
      208 npm
      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 28 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and the long descriptions clarify boundaries (e.g. check_tracking vs get_tracking_instructions, list_teams vs get_team vs list_team_goals). A few pairs overlap: get_campaign vs fetch(campaign:<id>), and get_stats vs get_program_overview both return revenue/commission snapshots. These are distinguishable from the descriptions but require reading them carefully.

    Naming Consistency4/5

    The vast majority follow a snake_case verb_noun pattern (list_campaigns, create_conversion, update_affiliate_status). Deviations are the bare generic verbs `search` and `fetch` and the vague `switch_from_another_tool`. Minor inconsistencies, still readable.

    Tool Count3/5

    28 tools is heavy and sits above the comfortable range, though the domain is genuinely broad (onboarding, campaigns, affiliates, conversions, coupons, payouts, teams, tracking). Several tools are informational rather than operational (get_linkjolt_plans, plan_affiliate_program, switch_from_another_tool), and some list/get pairs could likely be consolidated.

    Completeness4/5

    The surface covers the affiliate lifecycle well: setup, campaigns, affiliates, conversions, coupons, payouts, teams, and tracking verification, plus search/fetch for lookup. Gaps remain — no delete/archive for campaigns or coupons, no single-affiliate get beyond search/fetch, and payouts/awards are read-only (some deliberately so). Agents can work around most of these via update or the dashboard.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources