Skip to main content
If your product already uses MCP, ActionX can be integrated as a remote MCP service instead of through a frontend SDK.

​
Core information

  • MCP endpoint: https://mcp.actionx.top/mcp
  • Legacy SSE compatibility: /sse and /message
  • Primary tool exposed today: ads.request
  • Authentication: Authorization, X-API-Key, or token

​
Minimal tool input

{
  "query": "best bluetooth headset",
  "response": "Here are a few good options.",
  "count": 3,
  "user_id": "u_001"
}

​
When MCP is the better choice

  • Your system is already built around MCP or tool calling
  • You do not need the frontend rendering layer from the SDK
  • You prefer to keep monetization calls inside the agent runtime
Continue to the full MCP integration guide.