Yooo,

The title is a little bit of clickbait because my actual intention was more along the lines of "vibe coders struggled, so we helped them." This is supposed to be a tutorial post.

Why?

Because a lot of people building things today aren't programmers at heart, and the struggle is real. We get hundreds of support messages every day for "bugs" that turn out to be caused by inexperience, incorrect assumptions, or simply not reading the docs.

After seeing the same pattern over and over, the solution became pretty obvious: add an MCP server and a CLI so Claude can check your work before you get frustrated at us.

So here's a small tutorial.

Claude is already pretty good at writing social posts, building dashboards, and generally figuring things out. Give it a brand\_voice.xml file or the shape of your data, and you're already halfway there.

# What [bundle.social](http://bundle.social) MCP actually does

The MCP server exposes our API as tools Claude can use.

* check if your API setup works
* list connected social accounts
* create/schedule/retry/fetch posts
* fetch post analytics
* fetch social account analytics
* import post history
* create comments
* bulk schedule from CSV
* create hosted portal links so users can connect their own accounts
* work with teams/workspaces

There are also platform helper tools for annoying stuff like

* subreddit requirements / flairs
* YouTube categories / playlists / regions
* LinkedIn mentions
* Google Business (like everything you need)
* TikTok trending music

There are a lot of things you can do, all available in the docs section on our landing.

# Setup

The MCP server runs locally through `npx`.

For Claude Code:

    claude mcp add bundlesocial \
      --env BUNDLESOCIAL_API_KEY=sk_live_... \
      -- npx -y bundlesocial-mcp

For Claude Desktop, add this to your `claude_desktop_config.json`:

    {
      "mcpServers": {
        "bundlesocial": {
          "command": "npx",
          "args": ["-y", "bundlesocial-mcp"],
          "env": {
            "BUNDLESOCIAL_API_KEY": "sk_live_..."
          }
        }
      }
    }

If you use multiple teams/workspaces, you can also set:

    BUNDLESOCIAL_TEAM_ID=team_...

Docs are here:

    https://info.bundle.social/api-reference/mcp

# The basic workflow

The main thing I would *not* do is this:

    Post this everywhere.

That is how you get garbagio. The better pattern is to make Claude inspect first.

Example:

    Check my bundle.social setup and list connected social accounts.
    
    Tell me which accounts can publish posts and which ones need extra channel selection.
    
    Do not create or schedule anything yet.

This matters because “social account” is rarely just one simple thing.

For example:

* Facebook usually needs a Page
* LinkedIn can be a personal profile or an organization
* Discord needs a server/channel
* Pinterest needs a board
* Reddit may need subreddit requirements and flair
* YouTube has categories, playlists and regions

So Claude should check the real setup before trying to create anything.

Otherwise, it starts guessing, and guessing + publishing tools = Slop top

# Drafting platform-specific posts

Once Claude knows what accounts are connected, you can ask it to draft different versions.

Example:

    We shipped MCP support for bundle.social.
    
    Draft platform-specific posts for LinkedIn, X, Bluesky and Reddit.
    
    LinkedIn should be more detailed and developer-focused.
    X should be short.
    Bluesky can be more casual.
    Reddit should be tutorial-style and not sound like a press release.
    
    Do not create or schedule anything yet.

Claude is already useful here.

The difference is that now the next step can happen in the same workflow instead of becoming manual copy-paste hell.

# Approval before scheduling

After Claude gives you the drafts, you review them and approve one version.

Example:

    Use version 2.
    
    Schedule the LinkedIn post for tomorrow at 9:00 UTC.
    Schedule the Instagram post for tomorrow at 9:10 UTC.
    Schedule the Bluesky post for tomorrow at 9:20 UTC.
    
    Create the Reddit post as a draft only.
    
    Return all post IDs, platforms and scheduled times.

This gives you a pretty sane human-in-the-loop flow:

1. Claude checks the setup.
2. Claude drafts the content.
3. Human approves the final version.
4. Claude creates/schedules the posts.
5. The API handles publishing.
6. Claude can later check analytics.

So you whip Claude for the boring API work, but it does not get to YOLO, WE BALLIN your company account.

(which is probably healthy)

# Media uploads

Media was one of the bigger reasons we wanted this.

A lot of AI social workflows are fake-useful until you need to attach an actual image or video, with the MCP server, Claude can upload media first and then use the uploaded media in a post.

Example:

    Upload ./demo-video.mp4.
    
    Prepare a LinkedIn post and an X post using that video.
    
    Show me the final copy and media attachment summary before scheduling anything.

Then, after review:

    Looks good.
    
    Schedule LinkedIn for tomorrow at 10:00 UTC and X for 10:15 UTC.
    
    Return the created post IDs.

That is much nicer than Claude saying:

>“Attach your video here.”

Thanks bro, very helpful.

# Analytics loop

The first post is not even the most interesting part.

The more interesting part is what happens after publishing.

Because once posts exist in [bundle.social](http://bundle.social), Claude can fetch analytics later and use them as context.

Example:

    Check analytics for the posts we scheduled last week.
    
    Group results by platform.
    
    Tell me which topic performed best, which format underperformed and what we should test next week.

Or:

    Pull analytics for this post: post_abc123.
    
    Explain why it may have performed better than our previous launch post.
    
    Draft a follow-up post for LinkedIn and X.

# Why the “no account limits” thing matters

This is the part people glaze us for the most.

A lot of social media tools are priced around seats or connected accounts. I get it, it **PRINTS** money, but it's terrible for clients, and if you are building for

* agencies
* SaaS products
* franchises
* multi-location brands
* creator networks
* internal tools
* products where end users connect their own social accounts

uuuuuuhhh you aaaare getting rinced.

We do not do artificial connected account limits, usage limits and official platform limits still exist, obviously.

Meta is still Meta. TikTok is still TikTok.

But connected accounts are not the thing we cap, which makes MCP workflows nicer because Claude can work across a real multi-account setup instead of one hardcoded social profile.

# Example full prompt

    Check my bundle.social setup and list connected social accounts.
    
    Then draft a launch announcement for our new MCP server.
    
    Create separate versions for LinkedIn, Bluesky and IG.
    
    For IG, make it tutorial-style with graphics.
    For LinkedIn, explain the developer workflow in more detail.
    For Bluesky, make it more casual.
    
    Do not create or schedule anything until I approve.

Then after approval:

    Use the approved versions.
    
    Schedule LinkedIn for tomorrow at 9:00 UTC.
    Schedule X for 9:10 UTC.
    Schedule Bluesky for 9:20 UTC.
    
    Create the Reddit post as a draft.
    
    Return all post IDs, platforms and scheduled times.

Package:

    npx bundlesocial-mcp

Docs:

    https://info.bundle.social/api-reference/mcp

Also, if you are a data nerd, we have raw unparsed analytics: [https://info.bundle.social/api-reference/platforms/instagram#raw-analytics-demographics-&-audience-data](https://info.bundle.social/api-reference/platforms/instagram#raw-analytics-demographics-&-audience-data)

Vibe coding a social media SaaS? We built an MCP server that can manage unlimited accounts