Kickbacks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KICKBACKS_API_KEY | Yes | API key from Kickbacks.ai | |
| KICKBACKS_USER_ID | No | Your Kickbacks user ID | |
| KICKBACKS_API_BASE | No | Custom API base URL (default: https://api.kickbacks.ai/v1) |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kickbacks_balanceA | Get current Kickbacks.ai balance. Shows total earnings available for withdrawal. Requires KICKBACKS_API_KEY environment variable. Contact support@kickbacks.ai for API access. |
| kickbacks_earningsA | Get Kickbacks.ai earnings breakdown by time period: today, this week, this month, and all-time total. Requires KICKBACKS_API_KEY environment variable. |
| kickbacks_statusA | Get Kickbacks.ai connection status and earning state. Shows whether connected, authenticated, enabled, and if hourly/daily earning caps have been hit. Requires KICKBACKS_API_KEY environment variable. |
| kickbacks_ads_historyA | Get recent ad impression and click history. Shows each ad shown, campaign name, surface (spinner/statusbar), event type, revenue earned, and whether it was clicked. Supports pagination. Requires KICKBACKS_API_KEY environment variable. |
| kickbacks_set_enabledA | Enable or disable Kickbacks.ai ads. When disabled, no ads are shown and no earnings accrue. When enabled, ads appear in supported AI agent spinners and status bars. Requires KICKBACKS_API_KEY environment variable. |
| kickbacks_configA | Check Kickbacks.ai configuration status. Shows whether API key is set and provides setup instructions if not. Safe to call - never exposes secrets. |
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 6 tools
Every tool has a clearly distinct purpose: history, balance, config, earnings, enable/disable, and status. No ambiguity between them.
All tools follow a consistent 'kickbacks_' prefix with a descriptive noun or verb_noun pattern (e.g., ads_history, set_enabled). No mixing of conventions.
With 6 tools, the server is well-scoped for a monetization service. Each tool covers a core aspect (history, balance, earnings, config, enable/disable, status) without bloat.
The set covers key operations: viewing earnings/balance/history, checking config and status, and toggling ads. Minor gaps like withdrawal or detailed settings exist but don't hinder basic functionality.