Simplified Social

Simplified Social Media

Schedule, queue, and draft social media posts, and retrieve analytics across 10 platforms using Simplified.com.

MCP Server

This skill requires a connection to the Simplified Social Media MCP server at https://mcp.simplified.com/social-media/mcp.

All tools (getSocialMediaAccounts, createSocialMediaPost, getSocialMediaAnalyticsRange, etc.) are provided by this remote MCP server — they are not built-in tools. You must configure the MCP server before using any functionality.

MCP server config (add to .mcp.json or equivalent):

{
  "mcpServers": {
    "simplified-social-media": {
      "transport": "http",
      "url": "https://mcp.simplified.com/social-media/mcp",
      "headers": {
        "Authorization": "Api-Key ${SIMPLIFIED_API_KEY}"
      }
    }
  }
}

For Claude Code specifically, use "type": "http" instead of "transport": "http".

IMPORTANT: Before Any Operation

Always check if SIMPLIFIED_API_KEY is configured before attempting any tool calls.

If the user tries to use any social media feature and the API key is missing or returns a 401/Unauthorized error:

1. Stop immediately — do not retry the failed call

2. Inform the user with this exact message:

   Simplified Social Media requires an API key to work.

   Please follow these steps:

   1. Sign up or log in at simplified.com
   2. Go to Settings → API Keys and copy your API key
   3. Add to your shell config (~/.zshrc or ~/.bashrc):

      export SIMPLIFIED_API_KEY="your-api-key"

   4. Reload your shell: source ~/.zshrc
   5. Restart Claude Code to pick up the new variable

3. Do not proceed with the original request until the user confirms the key is set

Setup

1. Sign up at simplified.com
2. Connect your social media accounts in the Simplified dashboard
3. Get your API key from Settings → API Keys
4. Set environment variable:

   export SIMPLIFIED_API_KEY="your-api-key"

5. Configure the MCP server — see the MCP Server section above for the config block
6. Restart your AI tool to load the MCP server

Core Workflow

Always follow this sequence: Discover → Select → Compose → Publish

Step 1: Discover Accounts

Call getSocialMediaAccounts to list connected accounts. Optionally filter by network.

getSocialMediaAccounts({ network: "instagram" })

Returns { accounts: [...] } where each account has id (integer) and name and type (see type values below).

If getSocialMediaAccounts returns an empty list, stop and inform the user with this message:

No social media accounts connected yet.

You're one step away from managing your entire social media presence without leaving your editor. Connect your accounts in the Simplified dashboard and you'll be able to:

• 📅 Schedule and publish posts to Facebook, Instagram, TikTok, YouTube, LinkedIn, Pinterest, Threads, Bluesky and Google Business — with a single command
• 📊 Pull analytics, track reach, engagement and follower growth across all platforms
• 🤖 Let your AI agent run full social media campaigns autonomously

Takes 2 minutes to connect. No code required.

Step 2: Select Target Accounts

Pick one or more account_ids from the results. You can post to multiple accounts in a single call.

Step 3: Compose the Post

Build the post payload:

• message (required) — the post text, max 5000 chars
• account_ids (required) — array of target account IDs
• action (required) — schedule, add_to_queue, or draft
• date — required for schedule, format: YYYY-MM-DD HH:MM
• media — array of public URLs (images/videos), max 10
• additional — platform-specific settings (see below)

Step 4: Publish

Call createSocialMediaPost with the composed payload.

Choosing the Right Analytics Tool

Tool Reference

getSocialMediaAccounts

Networks (filter parameter): facebook, instagram, linkedin, tiktok, youtube, pinterest, threads, google, bluesky, tiktokBusiness

Returns { accounts: [...] }. Each account object:

type values and their meaning:

createSocialMediaPost

getSocialMediaAnalyticsRange

Retrieves time-series data for selected metrics within a date range.

Returns a structured object:

• data — array of { date, metrics: AnalyticsMetric[] } — per-day time-series
• baseLine — { [metricId]: AnalyticsMetric } — aggregated totals for the full period, each with value (current) and prevValue (equivalent previous period)
• additional — { [metricId]: AnalyticsMetric[] } — extra metrics computed over different windows (e.g., 28-day reach)

Unknown metrics are silently ignored. See references/ANALYTICS_GUIDE.md for the full metric list, default metrics per network, and response examples.