OFFICIAL CAELARIO MCP PACKAGE

Social media data,
native to your agent.

Give Codex or Claude Code typed tools for five social platforms, immediate answers, durable batches and recurring schedules. One Caelario key; no per-platform login setup.

NPM PACKAGECodex · Claude Code

One guided command

The installer prompts for your workspace key and registers the server for you. No JSON or TOML editing.

npx -y caelario-mcp install codex
npx -y caelario-mcp install claude
Requires Node.js 20+. Restart the selected client after installation. GitHub source ↗ · View on npm ↗ · Official MCP Registry ↗
01 Codex02 Claude Code21 focused tools55 operations
WHAT THE AGENT RECEIVES

More than an
HTTP wrapper.

The package teaches the client how to plan, price, run and retrieve Caelario work. Actual social-network sessions and anti-abuse infrastructure remain private on Caelario servers.

01

Plan without surprises

Discover platforms and exact operation limits, inspect pricing, and estimate the maximum credit reservation before starting.

02

Answer now

Run one bounded target synchronously and return a model-safe page of structured results in the same conversation.

03

Keep large work durable

Create jobs and hundred-target batches, wait for completion, cancel safely, and page large results without flooding context.

04

Automate repeat research

Create and manage once, daily, weekly, or monthly schedules with durable history in the same Caelario workspace.

A NORMAL AGENT RUN

Discover. Estimate.
Extract. Retrieve.

  1. 01Understand the requestThe agent checks the live catalog and correct target format.
  2. 02Show the cost for large workLimits and maximum reservations are visible before execution.
  3. 03Choose immediate or durable modeOne bounded target can answer inline; larger work gets a durable ID.
  4. 04Return only useful contextResults are paginated so large datasets do not overwhelm the conversation.
THE BOUNDARY

Your key stays local.
Provider identities do not.

The npm package runs locally over stdio. The customer’s Caelario API key is stored in the selected MCP client’s private user configuration and sent only to the configured Caelario API origin.

Instagram, TikTok, YouTube, X and Facebook accounts, cookies, proxies and browser identities are never MCP inputs. Those remain managed and isolated inside Caelario.

READY FOR AN AGENT-NATIVE WORKFLOW?

Connect once.
Ask in plain English.

Create your API key