LinkJoltDevelopers

Manage API Keys

← Back to LinkJolt.io

MCP SERVER

Use LinkJolt with Any MCP-compatible Client

The LinkJolt MCP server uses standard stdio transport and is compatible with any Model Context Protocol client. This includes Zed, Continue, Sourcegraph Cody, Taskade Genesis, custom agents, or your own integration.

Setup
1
Install the LinkJolt MCP server

Install the npm package globally, or use npx to run it on demand.

# Global install
npm install -g @linkjolt/mcp-server

# Or run via npx (no install)
npx -y @linkjolt/mcp-server
2
Get your API key

Generate a key at linkjolt.io/merchant/api-keys. Pro plan = read-only access, Ultimate = full read + write.

3
Configure your MCP client

Most MCP clients accept a JSON config. Use stdio transport with the config below. Adjust paths/env keys to match your client's format.

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

The server exposes 7 tools (list_campaigns, get_campaign, list_affiliates, list_conversions, get_stats, create_conversion, update_conversion). Your client should list them once connected.

Example Queries

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

list_campaigns — returns all your active campaigns
get_stats { from: "2026-01-01" } — aggregate revenue + commissions
list_conversions { status: "pending" } — conversions awaiting approval
create_conversion { campaignId, affiliateId, amount } — manual conversion

Official your client MCP docs

https://modelcontextprotocol.io/clients