Getting Started
Guides
REST API: Campaigns
Affiliates
Conversions
Affiliate Teams
SCALE
Coupons
Payouts
Other
Webhooks
LinkJolt works with any Model Context Protocol client, two ways: the hosted Streamable HTTP endpoint (OAuth sign-in for connector apps, or an API key header), or the npm package over stdio. This covers Zed, Continue, Sourcegraph Cody, custom agents, or your own integration.
Point your client at the URL below (Streamable HTTP). OAuth-capable clients discover the LinkJolt sign-in flow automatically from a 401 challenge; clients that support custom headers can send an API key instead.
{
"mcpServers": {
"linkjolt": {
"url": "https://www.linkjolt.io/api/mcp",
"headers": {
"Authorization": "Bearer lj_pk_your_key"
}
}
}
}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-serverGenerate a key at linkjolt.io/merchant/api-keys. Pro plan = read-only access, Ultimate = full read + write.
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"
}
}
}
}Your client should list the LinkJolt tools once connected: reads across campaigns, affiliates, conversions, coupons, payouts, teams and stats (list_campaigns, get_stats, and friends) plus three writes (create_conversion, update_conversion, create_coupon). The full table lives on the MCP overview page.
Once connected, ask your client natural language questions about your affiliate program:
Official your client MCP docs
https://modelcontextprotocol.io/clients