The Juicer MCP server lets your AI agent—Claude, Cursor, Windsurf, or any MCP-compatible client—control your Juicer account through natural language. Instead of opening the dashboard, you can ask your agent to create a feed, add a source, search posts, run moderation, set up webhooks, and more. This article explains how to get your API key and point your agent at the server.
What your agent can do
Once connected, your agent has access to all major Juicer features.
Feeds — list, create, update, and delete feeds, or get the embed code for any feed.
Sources — add or remove social media sources from any feed.
Posts and moderation — browse posts, approve or block individual posts, or moderate in bulk.
Search and Data API — full-text search across posts and access the Data API for exports and reporting.
Social accounts — list connected accounts, generate a reconnect URL, or remove an account.
Analytics — pull view and engagement data for any feed.
Webhooks — list, create, update, test, or delete webhooks.
Team management — add or remove users and assign feeds to team members (Enterprise accounts).
Your plan limits apply the same way they do in the dashboard. If an action is not available on your plan, the agent will receive an error message. See the pricing page to compare plans.
Step 1: Get your API key
Your API key authenticates the agent's requests to Juicer. Create a separate key per integration so you can revoke one without affecting the others.
Open your API dashboard.
Click Generate key (or Generate API key if you have no keys yet).
In the Generate API key modal, give the key a Key name to tell keys apart (for example,
ClaudeorCursor), then click Generate key.
Copy the key now. It is only shown in full once, so paste it into your password manager before closing the modal.
⚠️ Important: Treat your API key like a password. Anyone who holds it has full access to your account. Never commit it to source control or share it in a public channel.
Step 2: Connect your AI agent
Point your MCP client at the Juicer server URL and provide your API key. The URL and authentication method are the same regardless of which client you use.
MCP server URL —
https://api.juicer.io/mcpAuthentication — pass your API key in the
Authorizationheader. ReplaceYOUR_JCR_API_KEYwith yourjcr_…key.
Authorization: Bearer YOUR_JCR_API_KEY
Most MCP clients have a settings panel where you add a new server. Enter the URL above and, when prompted for authentication, choose Bearer token or API key and paste your key. Some clients (such as Claude Desktop) use a JSON config file. Add an entry under mcpServers with the URL and your token in the headers block.
🌿 Tip: Some clients support OAuth instead of a pre-pasted key. On first connect without a token, the server opens a browser window where you sign in to Juicer and approve access. The client then stores a key automatically, so no manual copying is needed.
In your client's connector settings, add Juicer as a custom connector, name it, and enter https://api.juicer.io/mcp. Leave the optional OAuth Client ID and Secret blank, then click Add.
The connector appears but isn't linked yet. Click Connect to start the browser sign-in.
Juicer opens in your browser and asks you to authorize access. Check the account shown, then click Authorize — this creates a new API key named after the app, which you can revoke anytime from the API dashboard.
Once authorized, you're sent back to your client with the connection live. The key is stored automatically, so there's nothing to copy or paste.
Troubleshooting
The agent returns "Unauthorized" or a 401 error — your API key may be wrong, revoked, or missing. Open the API dashboard, revoke the current key, generate a new one, and paste it into your agent's settings.
The agent gets "Forbidden" on a specific action — some features (bulk moderation, Data API, team management) require a higher plan. Check whether the action is included in your plan on the pricing page.
Your MCP client does not accept the server URL — confirm you are using
https://api.juicer.io/mcpexactly (not/v1orwww.juicer.io/mcp) and that the token has no extra spaces.
If your agent still cannot connect, contact us with the exact error message your client is showing, the name of your MCP client, and the first six characters of the API key you are using (never the full key), and we will take a look.