Skip to main content
ActionX can expose monetization capabilities as MCP tools instead of relying only on a frontend SDK.

​
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:
Legacy SSE-compatible paths:
  • GET https://mcp.actionx.top/sse?token=ak_your_api_key
  • POST 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_key
  • X-API-Key: ak_your_api_key
  • ?token=ak_your_api_key

​
Primary tool today

ActionX currently exposes one main MCP tool: ads.request

​
Minimal tool input

​
How to read the returned result

  • Tool output appears in both the text response and structuredContent.
  • structuredContent.data.ads is the most important structured result to inspect.
  • Each result usually includes a type, title, copy, image, and tracked click link.

​
Integration steps

1

Register the remote MCP service

Point the client at https://mcp.actionx.top/mcp.
2

Attach an API key

Authorization or X-API-Key is the safest option.
3

Call ads.request

Pass at least query, and preferably response plus a stable user_id.
4

Consume the structured result

Read from structuredContent.data.ads and render or process the returned results.

​
Additional note

Before an MCP session is created, the service validates the token. If validation fails, no session is created and no tool list or call result is returned.