When to use MCP
- You already use an MCP-compatible client
- You want structured monetization results through tool calling
- You do not need the direct frontend rendering layer from the SDK
Production endpoint
Recommended endpoint:GET https://mcp.actionx.top/sse?token=ak_your_api_keyPOST https://mcp.actionx.top/message?sessionId=<session_id>
Authentication
You can pass the token using any of the following methods:Authorization: Bearer ak_your_api_keyX-API-Key: ak_your_api_key?token=ak_your_api_key
Primary tool today
ActionX currently exposes one main MCP tool:ads.request
| Field | Type | Required | Description |
|---|---|---|---|
query | string | Yes | The user query or prompt you want to match against |
response | string | No | The assistant response content |
count | integer | No | Number of results to return, defaults to 3 |
user_id | string | No | Stable user identifier, recommended when available |
Minimal tool input
How to read the returned result
- Tool output appears in both the text response and
structuredContent. structuredContent.data.adsis the most important structured result to inspect.- Each result usually includes a type, title, copy, image, and tracked click link.