Affilync MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AFFILYNC_TOKEN | Yes | JWT access token used for authentication with Affilync. | |
| AFFILYNC_API_URL | No | The API base URL for Affilync. | https://api.affilync.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health check — verify the Affilync API is reachable and your token is accepted. |
| getUserProfileA | Get your Affilync profile. Call this first to check if you are an affiliate or brand. |
| searchCampaignsB | Search for campaigns by name, description, or category |
| getNotificationsB | Get your recent notifications (approvals, payouts, messages) |
| listAvailableCampaignsA | List campaigns available to join as an affiliate. Shows active campaigns accepting new affiliates. |
| listMyLinksB | List all your affiliate tracking links |
| getEarningsSummaryA | Get your earnings summary — total, pending, available balance, paid out |
| listCommissionsA | List your individual commission records from conversions and sales |
| getClickAnalyticsA | Get click analytics — totals, today, this week, this month |
| listActiveCampaignsA | List campaigns you've joined and are currently active in |
| joinCampaignA | Apply to join an affiliate campaign. Some campaigns auto-approve. |
| generateAffiliateLinkB | Generate a tracking link for a campaign you've joined |
| requestPayoutA | Request a payout of your available earnings. IRREVERSIBLE — moves real money. Omitting the amount requests your full available balance. |
| listBrandCampaignsA | List all campaigns owned by your brand |
| getCampaignPerformanceA | Get detailed performance metrics for a campaign — clicks, conversions, revenue, EPC |
| listAffiliateApplicationsA | List affiliate applications for your campaigns |
| getBrandDashboardC | Get your brand's overall performance dashboard |
| listBrandAffiliatesA | List all affiliates working with your brand |
| createCampaignB | Create a new affiliate marketing campaign with a commission structure |
| decideApplicationA | Approve or reject an affiliate's application to join your campaign. Consequential — affects who can earn commissions on your campaign. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Tools are largely distinct with clear purposes, separating brand and affiliate roles. Potential overlap between campaign listing tools (listBrandCampaigns, searchCampaigns, listAvailableCampaigns, listActiveCampaigns) is resolved by descriptive text, but could still cause initial confusion.
Naming follows a consistent camelCase convention with verbs like list, get, create, join. Minor outliers like 'decideApplication' and 'ping' deviate from the pattern, but overall it is predictable and readable.
20 tools is well-scoped for an affiliate marketing server covering both brand management and affiliate participation. Each tool serves a distinct function without being excessive.
Core workflows for both roles are covered: brands can create campaigns, manage applications, view performance; affiliates can join, generate links, track earnings, and request payouts. Missing update/delete for campaigns and leave campaign for affiliates are minor gaps.