Skip to main content
Connect any MCP client to Juicer with just the server URL. Most clients handle authorization for you through a browser sign-in; if yours doesn’t, pass an API key as a bearer token instead.

​
Endpoint and transport

​
Authentication

The server accepts two ways to authenticate. Pick whichever your client supports. Connect with only the URL. The first time your client reaches the server it opens a browser, you sign in to Juicer and click Authorize, and the client receives a token automatically — there’s nothing to copy or paste. Behind the scenes, approving creates a named API key scoped to your account. You can review or revoke it anytime from the API dashboard.
Authorizing grants a client access to your feeds and team. Only authorize clients you trust, and revoke any you no longer use from the API dashboard.

​
API key (bearer token)

If your client doesn’t support OAuth, or you’re scripting against the server, pass a jcr_ API key directly as a bearer token and skip the browser flow:
Generate a key from the API dashboard or the device-authorization flow (see Authentication). Treat it like a password — never commit it to source control.

​
Connect

The first call opens your browser to authorize. Approve, and you’re connected.To skip OAuth and use an API key:
Restart your MCP client after adding the server or changing your key so the new configuration takes effect.

​
Next steps

Tool Catalog

The 33 tools you can now call, grouped by domain.

Overview

How the server works and how it relates to the REST API.