Skip to main content
The Juicer MCP Server lets AI agents drive the Juicer API through Model Context Protocol tools. Instead of writing REST calls by hand, an agent — Claude, Cursor, Windsurf, ChatGPT, or any MCP-capable client — connects to the server and calls Juicer tools to create feeds, add sources, moderate posts, pull analytics, manage the team, and look up social data.
Looking to let an agent search these docs instead of driving your account? See the Documentation MCP — a separate, read-only server for questions about the Juicer API. This page documents the action MCP Server that operates on your feeds and data.

​
How it works

Each MCP tool call is dispatched through the same API chain that powers the REST API:
  • Authentication of your API key
  • Rate limiting for your plan tier
  • Quota and usage enforcement
  • The same controllers, validation, and serializers as the REST endpoints
The MCP Server holds no state of its own. It forwards every tool call to https://api.juicer.io/v1 with your token and returns the API’s response — including its structured error messages and upgrade hints — straight back to the agent. The result: the MCP Server returns the same data and enforces the same rules as the REST API.

​
Who it’s for

  • Agent builders wiring an LLM up to Juicer to automate feed and content workflows.
  • Claude Code and Cursor users who want to create feeds, add sources, and moderate posts from their editor.
  • Integrators onboarding and managing feeds on behalf of many clients from a single account.
Every action runs as your Juicer account, with your exact plan limits and permissions. Team management tools (inviting users, assigning feeds) require an Enterprise or Team plan and an owner or manager API key.

​
Endpoint and transport

​
Relationship to the REST API

The MCP Server is a thin, hosted wrapper over the public API — not a separate product.
  • The REST API is the underlying interface. Every endpoint is documented in the API Reference.
  • The MCP Server exposes those same operations as tools an agent can call. Each tool maps to exactly one endpoint.
Anything you can do over MCP, you can do over REST, and vice versa. Reach for MCP when an agent should decide which calls to make; reach for REST when you’re writing the integration yourself.

​
Next steps

Connect & Setup

Add the server to Claude, Cursor, VS Code, and more — with OAuth or an API key.

Tool Catalog

The 33 tools the server exposes, grouped by domain with scope and purpose.

Documentation MCP

A read-only server that lets agents search these docs in natural language.

API Reference

The REST endpoints every MCP tool maps to.