Documentation Index
Fetch the complete documentation index at: https://docs.getchatads.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
ChatAds provides a native MCP server that runs on our infrastructure. No local installation required - just point your MCP client directly to our endpoint.Quick Start
Add ChatAds to your MCP client’s configuration. The location varies by client:- Claude Code
- Claude Desktop
- Cursor
- Other Clients
Add to your user config at
~/.claude.json under the mcpServers key:Benefits
- No installation - Works immediately, no Python or dependencies
- Always up-to-date - Server updates apply automatically
- Team-friendly - Centralized configuration, consistent behavior
- Cross-platform - Works with any MCP-compatible client
Technical Details
Endpoint
Transport
The native server uses MCP Streamable HTTP transport, which:- Creates a session on first request
- Returns responses as Server-Sent Events (SSE)
- Maintains session state via
mcp-session-idheader
Authentication
All requests require thex-api-key header with your ChatAds API key.
Direct API Usage
You can also interact with the MCP endpoint programmatically using JSON-RPC 2.0.Required Headers
Step 1: List Available Tools
The server runs stateless — no session initialization required. You can call any method directly.Step 2: Call the Tool
Send an AI assistant response as themessage — this is what ChatAds scans for product mentions to turn into affiliate links.
Available Tools
chatads_message_send
The main tool for fetching affiliate product recommendations.| Parameter | Required | Type | Description |
|---|---|---|---|
message | Yes | string | User query (max 10,000 chars) |
extraction_mode | No | string | none or standard (default) |
resolution_mode | No | string | none or standard (default) |
max_offers | No | number | Max affiliate links to return, 1–3 (default: 1) |
max_products_per_offer | No | number | Max products per offer carousel, 1–3 (default: 1) |
ip | No | string | End-user IP for geo-targeting |
country | No | string | ISO 3166-1 alpha-2 country code |
metadata | No | object | Arbitrary JSON object (max 10KB) echoed back in the top-level metadata response field on successful data responses. Non-object or oversized values are replaced with {"error":"invalid input"}. |
Troubleshooting
”Missing API key” (401)
Ensurex-api-key header is included in your config:
“Invalid API key type” (403)
The MCP endpoint requires a ChatAds API key (cak_ prefix). Widget keys (cwk_) are not supported.
Make sure your key starts with cak_ — you can create one at app.getchatads.com.
”Client must accept both application/json and text/event-stream”
Add the proper Accept header:Tool not appearing in your MCP client
- Verify the URL is exactly:
https://api.getchatads.com/mcp/mcp - Check that
transportis set to"http" - Restart your MCP client completely
- Ask: “What tools do you have access to?”
Next Steps
Get API Key
Sign up and create your API key in the dashboard
Python SDK
Server-side integration with the Python SDK