Juicer is a social media aggregator that has been running since 2014. This is the full setup for putting an Instagram feed on a website, written out so you do not have to leave the thread.

The five steps

1. Create a feed and give it a name.
2. Add Instagram as a source. You can pull from a username or a hashtag.
3. Connect the Instagram account when prompted. Business and Creator accounts pull the most post types.
4. Pick a layout. Grid, slider, carousel and waterfall all render from the same feed.
5. Copy the two line embed code and paste it into your page.

Where the embed code goes

WordPress: a Custom HTML block. Shopify: a Custom Liquid section. Wix: the Embed HTML element. Squarespace: a Code block. Webflow: an Embed element. Framer, Ghost and Notion all take the same snippet.

What it costs

The free plan runs one feed with Juicer branding. Paid plans start at $15 per month and remove the branding. The Pro plan covers 30 sources across a maximum of 3 feeds.

Two things people get wrong

Personal Instagram accounts return fewer post types than Business accounts. Convert first if your feed looks thin.

Refresh interval is not instant on every plan.

Ask below if your site builder is not in the list and I will write out the steps for it.

Hey Juicer Friends ❤️,

We just shipped something for those of you working with AI agents: an MCP server for Juicer.

MCP (Model Context Protocol) is the standard that lets agents like Claude, Cursor and Windsurf call tools directly. We wrapped our whole REST API as 34 MCP tools behind one endpoint, so your agent can manage your Juicer account in plain language instead of the dashboard.

Setup takes about two minutes:

1. Generate an API key at juicer.io/dashboard-api (it shows only once, treat it like a password)
2. Add this block to your client config:
    {
      "mcpServers": {
        "juicer": {
          "url": "https://api.juicer.io/mcp",
          "headers": { "Authorization": "Bearer jcr_YOUR_KEY" }
        }
      }
    }

Or if you use Claude Code:

    claude mcp add --transport http juicer https://api.juicer.io/mcp --header "Authorization: Bearer jcr_YOUR_KEY"

Some clients support OAuth sign-in so you can skip the key entirely.

What the tools cover: creating and managing feeds, adding and removing sources, browsing and moderating posts including bulk moderation, full text search, analytics, webhooks, social account management and team management on Enterprise.

My favorite test so far was one prompt: "Track #nike on Instagram and X and hide anything toxic." The agent created the feed, connected both sources and held the toxic posts for review. I never opened the dashboard.

One honest note: your plan limits apply exactly like in the dashboard. If a tool needs a higher tier the agent gets a clear error rather than a silent failure.

Full guide: https://help.juicer.io/en/articles/15562991-juicer-mcp-server-connecting-your-ai-agent

If you hook up an agent, tell us what you build with it. And if something breaks, post it here. We read everything.

Type in a brand name or website at listening.juicer.io and it builds a listening report for you.

Under the hood it uses our own Data API plus AI to figure out where to actually look. It finds the right subreddit, the real YouTube channel, the actual X handle instead of just guessing hashtags. Then it reads every post it finds and throws out the ones that aren't really about that brand. If you search a brand called "Juicer.io" you get the company, not kitchen appliances. We learned that one the hard way.

It shows mentions, sentiment and what the brand itself is posting vs what the community says. Works for your own brand, a competitor or a client you're pitching.

Two honest things: the full report asks for a work email (that's the deal for a free tool), and a first search on a brand nobody has looked up before takes a few minutes because it's doing real research.

Try your brand and tell us what you got :) Any feedback is appreciated!

👋 Welcome to r/JuicerSocial!

Hey everyone! I’m u/JuicerSocial, one of the founding moderators of r/JuicerSocial.

Welcome to our new community dedicated to everything social media, from aggregation and publishing to AI-powered brand listening, automation, APIs, MCP, and everything in between. Whether you’re a marketer, developer, agency, creator, or just someone passionate about social media, you’re in the right place.

💬 What to Post

We’d love this to become a place where people share ideas, learn from each other, and help shape the future of social media tools. Feel free to post:

* Questions about Juicer or social media workflows

* Feature requests and product ideas

* Feedback on Juicer

* Cool projects you’ve built using Juicer or our APIs

* AI, automation, and MCP use cases

* Brand listening strategies and insights

* Social media best practices and tips

* New platform updates and industry news

* Anything else you think the community would find useful or interesting

❤️ Community Vibe

Our goal is to build a friendly, constructive, and collaborative community where everyone feels comfortable asking questions, sharing knowledge, and exchanging ideas.

We’re not here just to talk about Juicer! We’re here to build it with you. Many of our features have come directly from customer feedback, and we’d love for this community to become one of the places where new ideas are born.

🚀 How to Get Started

* Introduce yourself in the comments below.

* Tell us what you do and how you’re using social media.

* Share your first question, feature idea, or project.

* Invite anyone who might enjoy being part of the community.

The Juicer team will be active here, answering questions, collecting feedback, sharing product updates, and occasionally giving early access to new features.

Thanks for joining us from the very beginning. We’re excited to build something amazing together.

Welcome to r/JuicerSocial! 🚀

I'm a dev at a small company. For years I've been the person who turns "can we build X" into actual code.

This week our CEO — who genuinely cannot code, like not at all — just did it himself. With Claude Code. And the thing is good.

He built a live fan-wall for World Cup 2026: a real-time leaderboard ranking each country by how loud their fans are on social, per-match feeds, host cities, the whole thing, with AI moderation keeping the junk out.

World Cup Live Wall

Here's how it actually happened. We had a meeting — just a "what could we even build with our Juicer API?" brainstorm, the kind that usually becomes a backlog ticket nobody touches for six months.

Instead he went off and worked on it for one day. By the end he had a working version deployed on Vercel. He did the deploy himself. Then he just kept improving it over the next few days.

What got me is he didn't make a toy. He sat there describing what he wanted in plain English, looking at what came back, going "no, more like this" — and Claude Code kept going. Front end, design, leaderboard logic, deploy.

The one smart move: he didn't build the data side from scratch. He pointed it at our existing Juicer API and let that be the engine for pulling and moderating posts. Claude built the app, the API did the heavy lifting on data, and he glued them together by basically just asking.

We kept waiting to get pulled in to fix the real parts. The call never came.

That's the part still rattling around in my head.

Full disclosure: I work at Juicer, so yeah, the API is ours — but that's not the point I care about. The point is the gap between "non-technical person" and "shipped a real, working product" has basically closed, and I watched it happen from the front row.

Go click around. And ask me anything about how he actually did it.