AiToEarn
Drafts, schedules, publishes, and comments on the social accounts you link on its own side, so one hosted MCP endpoint drives posting as you while the bot never holds a platform password.
What it provides
Connect an existing HTTPS deployment, with a scoped token where the service requires one. Heavy jobs stay on that service instead of using bot memory.
Connection requirements
A key is required here, not optional. Create an AiToEarn account, generate an API key there, and keep the x-api-key mode selected. There are two separate deployments with separate keys: use https://aitoearn.ai/api/unified/mcp with an aitoearn.ai key, or https://aitoearn.cn/api/unified/mcp with an aitoearn.cn key. A key from the wrong environment is rejected as Unauthorized rather than returning a tool list, so run `mcp tools` first to confirm the pairing before wiring anything else up. Understand the reach of that key before you paste it: the endpoint is not read-only and not limited to scheduling. It also exposes tools that publish immediately (publishChannelTaskNow), reschedule or cancel a queued post (updateChannelPublishAt, cancelChannelPublishTask), delete drafts (deleteDraft), post public comments and other engagement as your linked accounts (submitChannelEngagementComment, callChannelEngagementFunction), and generate drafts through paid AI jobs (createVideoDraft). The publishing and engagement tools act through your linked accounts and what they post becomes publicly visible as you, so treat this like handing over posting rights and start on an account you can afford to have the agent act on. The platform credentials and OAuth grants stay on AiToEarn’s side and the bot only holds this API key. If you self-host the Docker deployment instead, point the endpoint at your own host and mint the key there.
- Protocol
- Streamable HTTP MCP
- Endpoint
https://aitoearn.ai/api/unified/mcp- Authentication
- x-api-key
mcp toolsmcp call listChannelPlatforms {}Where to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.