How to Let AI Run Your Social Media: Claude, Codex, Cursor and More (Full MCP Setup)

Quick Answer

Create an API key in Autoadify under Settings → API & MCP, add the server https://mcp.autoadify.com/mcp to your assistant with that key as a Bearer header, and ask it to schedule a post. Claude Code, Codex, Cursor, Gemini CLI, VS Code and Claude Desktop all work. One request can publish different text to each of 9 networks, and every post lands in your Autoadify calendar where you can still see and edit it.

Your AI assistant can already write your posts. It just can't post them. So you copy, paste, open six tabs, upload the same image six times and fix the character count for X by hand.

We built Autoadify's MCP server to remove that copy-paste step. Here is what it gets you:

• Claude, Codex, Cursor, Gemini CLI or VS Code can post to Instagram, Facebook, LinkedIn, X, TikTok, YouTube, Reddit, Bluesky and Threads
• Different text per platform, from one request
• Your media library, searchable by what is actually in each image
• Everything lands in your Autoadify calendar, so you can still see and edit it

1. Get a key (2 minutes)

In Autoadify, go to Settings → API & MCP and click Create key. Give it Read and Publish.

Limit the key to the channels you want the assistant to touch, and start with one test channel. Publishing is real, so posts go out on your actual accounts.

The key starts with aak_live_ and is shown only once, so store it in your password manager. API and MCP access are on paid plans, from Pro at $29/mo.

2. Connect your assistant

One server URL for everything: https://mcp.autoadify.com/mcp

Claude Code

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

Cursor

Add it to ~/.cursor/mcp.json:

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

Codex

Put your key in an environment variable, then add the server:

export AUTOADIFY_API_KEY="aak_live_..."
codex mcp add autoadify --url https://mcp.autoadify.com/mcp --bearer-token-env-var AUTOADIFY_API_KEY

Gemini CLI

Add it to ~/.gemini/settings.json:

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

VS Code, Claude Desktop and any other client that supports remote MCP with a custom header work too; the exact config for each is in the MCP docs. The ChatGPT app and the claude.ai web app cannot send an API key header to a custom server yet, so use Codex or Claude Code for now.

3. Ask it what it can see

Before you post anything, run this:

What channels do I have connected, and what does each one need before I can post to it?

This calls list_channels. You get every account plus its rules: Instagram needs an image or video, X caps your characters, Reddit needs a subreddit. Your assistant knows the rules before it writes a single word, which prevents most "why did this fail" moments.

4. Write once, post everywhere — properly

Here's our announcement: [paste it]. Schedule it to LinkedIn and X for Tuesday 9am IST. Keep the full version for LinkedIn. Write a punchier version under 280 characters for X. Show me both versions and the time before you schedule anything.

One post, two versions, one request. Under the hood it is a single post with per-platform text, so it shows up as one item in your calendar. The "show me before you schedule" line matters: good assistants confirm first anyway, but say it out loud.

5. Let it find the image for you

Most media libraries are a pile of IMG_4471.JPG. Autoadify describes what is actually in each file, so the assistant can search by content:

Find a photo from our library that shows the product on a desk, and use it for an Instagram post tomorrow at 6pm about our new feature.

Not in the library yet? Give it a link:

Import this image and post it to Instagram tomorrow morning: [URL]

In Claude Code, it can even upload a file straight from your computer.

6. Run your week from one chat

Once it is connected, the calendar is a conversation. Prompts worth using every Monday:

What's scheduled for next week?

Move Friday's post to Monday, same time.

Did yesterday's posts go out? If any failed, tell me why.

That last one is underrated. Every post comes back with its status per platform, the live link, and the exact error if something failed — such as a connection that needs reconnecting. The errors are written so the assistant can fix the request, not just report "400".

7. Guardrails

These are your real accounts, so:

• Scope the key. A read-only key gives the assistant no tools that change anything — good for a reporting agent.
• Limit channels. Give a test key one channel until you trust the flow.
• Same rules as the app. Platform requirements, plan limits and our content policy all still apply.

Frequently Asked Questions

Which AI assistants work with Autoadify's MCP server?

Any client that supports remote MCP over HTTP with a custom header: Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI and VS Code. The ChatGPT app and claude.ai on the web cannot send the API key header yet.

Will the assistant post without asking me?

It can publish if the key has the Publish permission, so ask it to show you the text and time before scheduling, start with a single test channel, or use a read-only key for assistants that should only report.

Do I need a paid plan?

Yes. API keys and MCP access are available on paid plans, starting with Pro at $29/mo.

The Bottom Line

No more copy-paste between six tabs. You or your AI write the post, and the AI schedules it — with the right text for each platform and everything visible in one calendar.

Building your own app instead? The same keys work with our REST API: see how to schedule posts to 9 platforms with one API call, or read the MCP server overview.