agentfuse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTFUSE_API_KEY | Yes | Your AgentFuse API key (af_live_...) | |
| AGENTFUSE_API_URL | No | Override the API base URL | https://api.agentfuse.io |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_affiliate_programsA | Browse available affiliate programs in the AgentFuse catalog. Returns each program's name, slug, category, commission rate, and network. Use this to discover programs before generating tracked links. |
| get_affiliate_programA | Get full details for a single affiliate program by its slug. Returns the program's UUID (needed for generate_tracked_link), commission structure, payout terms, description, and network info. |
| generate_tracked_linkA | Generate a tracked affiliate link for a program and an end user. Pass the human-readable program slug (e.g. 'webflow') -- the tool resolves the UUID automatically. The link records clicks and attributes any resulting signups or commissions back to the specified end user. Returns a short redirect URL and a tracking_code you should save -- it is needed for record_signup and record_commission. |
| get_statsA | Retrieve AgentFuse dashboard summary stats: total clicks, signups, commissions, and top-performing programs. Useful for reporting to users or surfacing revenue data. |
| list_tracked_linksA | List tracked affiliate links previously generated by this API key. Returns each link's tracked URL, tracking_code, click count, program, and end user. Use this to look up existing links before generating a new one, or to show a user their active referral links. |
| record_signupA | Record an affiliate signup conversion event. Call this when one of your end users successfully signs up for a referred product. Requires the tracking_code returned by generate_tracked_link. Idempotent -- safe to call multiple times with the same network + network_event_id. |
| record_commissionA | Record an affiliate commission event (e.g. when a referred user makes a purchase or renews a subscription). Requires the tracking_code from the original affiliate link. Idempotent -- safe to call multiple times with the same network + network_event_id. |
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 7 tools
Each tool has a clear, unique purpose: generating links, retrieving program details, listing resources, recording different event types, and fetching stats. No two tools overlap in functionality; even record_commission and record_signup are distinctly about different events.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., generate_tracked_link, list_affiliate_programs, record_commission). The naming is predictable and easy to understand.
With 7 tools, the server is well-scoped for an affiliate link tracking service. Each tool serves a necessary function without being overwhelming or too sparse.
The tool surface covers core use cases: browsing programs, creating tracked links, listing links, recording signups and commissions, and viewing stats. Minor gaps like updating or deleting links exist but are not critical for the primary workflow.