aibrandblast-mcp

Official Model Context Protocol (MCP) server for AIBrandBlast — generate AI social media content, schedule posts, and check your connected accounts directly from Claude Desktop, Claude Code, or any other MCP-compatible client.

Requires an AIBrandBlast Agency plan API key. Get one at aibrandblast.com/social.

Quickstart

No installation needed — run it directly with npx:

npx aibrandblast-mcp

On its own this just starts the server on stdio waiting for an MCP client to connect. In practice you'll point an MCP client at it using the config below.

Setup: Claude Desktop

Add this to your Claude Desktop config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "aibrandblast": {
      "command": "npx",
      "args": ["aibrandblast-mcp"],
      "env": {
        "AIBRANDBLAST_API_KEY": "your-api-key-here"
      }
    }
  }
}

Restart Claude Desktop after saving. AIBrandBlast's tools will show up in the tools list (hammer icon).

Setup: Claude Code

Add the same server via the CLI:

claude mcp add aibrandblast -e AIBRANDBLAST_API_KEY=your-api-key-here -- npx aibrandblast-mcp

Or add it directly to your .mcp.json:

{
  "mcpServers": {
    "aibrandblast": {
      "command": "npx",
      "args": ["aibrandblast-mcp"],
      "env": {
        "AIBRANDBLAST_API_KEY": "your-api-key-here"
      }
    }
  }
}

Configuration

| Environment variable | Required | Description | |---|---|---| | AIBRANDBLAST_API_KEY | Yes | Your AIBrandBlast Agency plan API key. Get one from aibrandblast.com/social. The server exits immediately with a clear error if this isn't set. | | AIBRANDBLAST_BASE_URL | No | Override the API base URL. Defaults to https://aibrandblast.com. Useful only for self-hosted or staging environments. |

Tools

generate_content

Generate AI social media content for a business.

Parameters:

• business (string, required) — description of the business (name, industry, tone, anything relevant to write about)
• type (string, optional) — content type, e.g. linkedin_post or social_post. Defaults server-side if omitted.
• customPrompt (string, optional) — extra instructions to steer the generated content

Example prompts to Claude:

"Write a LinkedIn post for my coffee shop, Bean There Done That, announcing our new oat milk lineup."

"Generate a social post for my HVAC company promoting our summer tune-up special."

schedule_post

Schedule a post, or send it to pending approval if no time is given.

Parameters:

• content (string, required) — the post text
• platforms (string array, required) — target platforms, e.g. ["linkedin", "twitter"]
• scheduled_at (string, optional) — ISO 8601 datetime (e.g. 2026-07-10T13:00:00-04:00). Claude resolves phrases like "tomorrow at 9am" to this format for you. If omitted, the post goes to pending approval instead of being scheduled.

Example prompts to Claude:

"Schedule that last post to LinkedIn and Twitter for tomorrow at 9am."

"Queue this caption for Instagram — I'll approve it manually later."

list_scheduled_posts

Lists your most recent scheduled, pending-approval, and posted content (up to 50, most recent first) — content, platforms, scheduled time, status, and any posting errors.

Example prompts to Claude:

"What do I have scheduled this week?"

"Show me anything that failed to post."

list_connected_accounts

Lists the social accounts currently connected to your AIBrandBlast account.

Example prompts to Claude:

"Which social accounts do I have connected?"

"Is my Instagram still connected before I schedule this?"

A typical workflow

"Write a LinkedIn post for my dispensary about our new pre-roll line, then schedule it for tomorrow at 9am."

Claude will call generate_content, show you the draft, and — once you approve it — call schedule_post with an ISO 8601 timestamp for "tomorrow at 9am" resolved against the current date.

Requirements

• Node.js 18 or later
• An AIBrandBlast Agency plan account and API key

Troubleshooting

"missing required environment variable AIBRANDBLAST_API_KEY" — set AIBRANDBLAST_API_KEY in your MCP client's server config (see Setup above).

HTTP 401/403 errors — your API key is invalid, expired, or your AIBrandBlast plan doesn't include API access. API access requires the Agency plan.

Network / connection errors — check that https://aibrandblast.com is reachable from your machine, or that AIBRANDBLAST_BASE_URL (if set) points to a reachable host.

License

MIT