---
source: https://autoadify.com/mcp
title: "Autoadify MCP server"
---

# Autoadify MCP server

> The Autoadify MCP server gives an AI assistant 13 tools for a social media workspace: see connected channels and their rules, schedule or publish posts, track whether they went out, and manage the media library. Included on paid plans from Pro.

Server URL: `https://mcp.autoadify.com/mcp` (Streamable HTTP) · Documentation: https://docs.autoadify.com/mcp/overview

## Tools

- `whoami` (read) - The workspace, plan, permissions and remaining quota of the key.
- `list_channels` (read) - Connected channels with each platform's posting rules — media required, image limits, text length, required fields.
- `create_post` (publish) - Schedules a post to one or many channels, or publishes it now. Per-platform text, media, Reddit and TikTok options.
- `list_posts` (read) - Posts with their status on each channel, filtered by status, channel or date.
- `get_post` (read) - One post: status per channel, the live URL, and the error if a channel failed.
- `update_post` (publish) - Edits a scheduled post's text, per-platform text or time.
- `delete_post` (publish) - Cancels a scheduled post.
- `list_media` (read) - Searches the media library by name, alt text and a description of what each file shows.
- `get_media` (read) - One file: status, URL, type, size and dimensions.
- `import_media` (publish) - Pulls an image, video or PDF from a public URL into the library.
- `create_media_upload` (publish) - A one-time URL for uploading a local file, for agents with a shell.
- `complete_media_upload` (publish) - Finishes an upload once the file has been sent.
- `delete_media` (publish) - Deletes a file; refused while a scheduled post still uses it.

## Connect a client

Create an API key in Autoadify under Settings → API & MCP (https://app.autoadify.com/settings/developers), then:

### Claude Code

One command in your terminal.

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

### Cursor

~/.cursor/mcp.json

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

### VS Code

.vscode/mcp.json

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

### Claude Desktop

Settings → Developer → Edit config, via mcp-remote.

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

Any client that supports remote MCP servers over Streamable HTTP with a custom header works. The claude.ai and ChatGPT web connectors are not supported yet: they can't send an API key header, which this server requires.

## Control

- A read-only key sees no tool that changes anything.
- A key can be limited to chosen channels.
- Platform rules, plan limits and Autoadify's content policy apply as in the app.
- Publishing is real: posts go out on the connected accounts.

## Plans

- **Pro** ($29/mo) - 10,000 a month (60/min), shared with the REST API
- **Team** ($79/mo) - 100,000 a month (300/min), shared with the REST API
- **Enterprise** ($299/mo) - Unlimited (1,000/min), shared with the REST API

Not to be confused with connecting your own MCP servers to Autoadify's built-in agent, which is the reverse direction.

---

_Source: https://autoadify.com/mcp_