MCP server

• “What channels do I have connected?”
• “Schedule this announcement to LinkedIn and X for Tuesday 9am, with a shorter version for X.”
• “Import this image and post it to Instagram tomorrow morning.”
• “What’s scheduled for next week? Move Friday’s post to Monday.”

​

Connect your client

claude mcp add --transport http autoadify https://mcp.autoadify.com/mcp \
  --header "Authorization: Bearer aak_live_..."

{
  "mcpServers": {
    "autoadify": {
      "url": "https://mcp.autoadify.com/mcp",
      "headers": { "Authorization": "Bearer aak_live_..." }
    }
  }
}

{
  "servers": {
    "autoadify": {
      "type": "http",
      "url": "https://mcp.autoadify.com/mcp",
      "headers": { "Authorization": "Bearer aak_live_..." }
    }
  }
}

{
  "mcpServers": {
    "autoadify": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mcp.autoadify.com/mcp",
        "--header", "Authorization: Bearer aak_live_..."
      ]
    }
  }
}

​

How it behaves

• Only the tools your key allows. A read-only key sees no tools that change anything.
• Publishing is real. Posts go out on your actual accounts. Good assistants confirm the text, channels and time with you first; if you want to be safe, start with a key limited to one test channel.
• Same rules as the app. Platform requirements, plan limits and Autoadify’s content policy apply exactly as they do in the app.
• Same limits as the API. MCP calls count towards the same rate limit and monthly quota.