AFLINK / MCP
Aflink MCP: affiliate programs from your AI assistant
The Model Context Protocol (MCP) connects compatible AI tools with Aflink through permission-checked operations. You can inspect affiliate activity and manage approved business workflows without pasting API secrets into a chat.
Why use MCP?
Find your company workspaces, inspect programs, review links and commissions, or create a draft SaaS program from an authorized assistant. The underlying permissions and audit rules are the same as in Aflink.
Connect in a compatible client
- Open your AI client's MCP or integrations settings.
- Add a remote Streamable HTTP server using https://api.aflink.dev/mcp.
- Choose OAuth and sign in through CIATTO Account when prompted. Approve only the permissions you understand.
- Start with the aflink_session tool to identify your workspaces. Read-only operations require aflink:read; authorized changes require aflink:write. Some clients request offline_access for refresh.
- Try asking: "List my affiliate programs and explain their commission conditions."
Example client configuration
{
"mcpServers": {
"aflink": {
"type": "streamable-http",
"url": "https://api.aflink.dev/mcp"
}
}
}What can an assistant do?
Read account/workspace context, program lists, memberships, tracking links, commission ledger, payouts, integration metadata and audit logs. With the proper company role and write scope, it can create workspaces, register/edit SaaS programs, change program status, review memberships and manage tracking links.
What it cannot do
MCP does not accept affiliate legal terms, reveal or issue integration secrets, or initiate financial payouts. Program commissions and approvals remain governed by their own rules. An AI assistant must not be treated as a guarantee of outcomes.
For SaaS developers
MCP is a management interface, not the signed conversion-event API. The SaaS integration guide explains use of https://api.aflink.dev/v1/events. The public endpoint and OAuth resource are now on api.aflink.dev. Previously issued grants remain supported during the transition, but new connections should use this address.
Troubleshooting and safety
If consent or login fails, confirm your CIATTO Account onboarding and the client's remote MCP/OAuth support. Never paste access tokens or credentials into prompts. For help: [email protected].