Use LinkJolt with Claude

LinkJolt is listed in Claude's connector directory. In claude.ai or Claude Desktop, add it from there, approve access on a LinkJolt page, done. No API key to handle. Claude Code and stdio-only setups can use an API key instead.

Setup

claude.ai and Claude Desktop: add LinkJolt from the directory

Click "Add from the Claude directory" above. It opens LinkJolt's listing in Claude's connector directory, where you add it to your Claude account; it then shows up in Claude Desktop too. To add it by hand instead, as a custom connector: open Settings, then Connectors, then "Add custom connector", and fill in two fields only: Name (LinkJolt) and Remote MCP server URL (below). Leave OAuth Client ID and OAuth Client Secret empty under Advanced settings, since LinkJolt registers your client automatically. Available on every Claude plan (Free accounts can add one custom connector). On Team and Enterprise plans an organization Owner adds it once for everyone.

https://www.linkjolt.io/api/mcp

Approve access on the LinkJolt page that opens

Your browser opens a LinkJolt approval page (instantly if you're already signed in to LinkJolt; otherwise sign in with your merchant account first). The page lists exactly what Claude can read and write, scoped to your active brand, and the connector never sends money. Click Approve and setup is finished: nothing to install, no API key to copy, and you won't see this page again. Disconnect any time from Claude's connector settings.

Claude Code (terminal): add the endpoint, then sign in

Claude Code supports the same OAuth sign-in as the apps, so there is no key to create or paste. Add the server, then run /mcp inside Claude Code and authenticate; your browser opens the LinkJolt approval page. Use --scope user so the server is available in every project, not just the folder you ran the command in.

claude mcp add --transport http --scope user linkjolt \
  https://www.linkjolt.io/api/mcp

# then, inside Claude Code:
# /mcp  ->  select linkjolt  ->  authenticate

Claude Code alternative: use an API key instead

For CI or headless setups where no browser is available, send an API key header instead of signing in. Create a key at linkjolt.io/merchant/api-keys (Pro keys can read and set a program up, Ultimate and Scale keys can also record, approve and reject sales and add coupons). Paste your real key: with a placeholder the server still answers the tool list, so the connection looks healthy until the first tool call fails.

claude mcp add --transport http --scope user linkjolt \
  https://www.linkjolt.io/api/mcp \
  --header "Authorization: Bearer lj_pk_REPLACE_WITH_YOUR_KEY"

Alternative: local npm package (stdio)

Only for clients that cannot reach a remote server at all. It carries the same tools as the hosted endpoint, but not the prompts, and it needs an API key rather than the OAuth sign-in above. Use the hosted endpoint unless you are stuck on stdio.

{
  "mcpServers": {
    "linkjolt": {
      "command": "npx",
      "args": ["-y", "@linkjolt/mcp-server"],
      "env": {
        "LINKJOLT_API_KEY": "lj_pk_your_key_here"
      }
    }
  }
}

Example Queries

Once connected, ask Claude natural language questions about your affiliate program:

“Show me my top 5 affiliates by revenue this month”

“How many pending conversions do I have right now?”

“Approve conversion conv_abc123”

“What's my total commission paid out this quarter?”

“List all affiliates who joined in the last 7 days”

Official Claude MCP docs

https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

Need help?

Email ollie@linkjolt.io with what you asked Claude and what happened, and we will help you get it working.

← All MCP clients