Reeling API and MCP examples

Clone and run without credentials

Use Node.js 22 or later. The examples use Node’s built-in fetch and test runner and have no npm dependencies. The tests cover explicit channel selection, private/inbox defaults, per-platform failure handling, polling timeouts and ambiguous POST errors.

The default results are labeled offline fixtures. They demonstrate output shapes and recovery logic; they do not represent customer data or successful live posts.

git clone https://github.com/yomariano/reeling-examples.git
cd reeling-examples
npm test
node examples/read-account.mjs
node examples/poll-status.mjs
node examples/read-analytics.mjs

• Open reeling-examples on GitHub

Configure a real account read

Create a local ignored .env using the documented variable names. Use your own project and channel IDs. Node does not load the file automatically; pass --env-file=.env. The account script requires --live-read before it sends either discovery GET.

Your API key can authorize writes. The scripts constrain their operations, but the key itself is not read-only. Keep the file and live outputs out of source control.

node --env-file=.env examples/read-account.mjs --live-read

• Account read source
• API setup guide

Draft before publishing

Set the media URL, exact channel, project, caption and intended time locally. The scheduling script prints the request first without submitting. Review the destination, visibility and audience settings before adding --publish.

The example selects one channel per invocation and defaults to private YouTube visibility and TikTok inbox delivery. For several destinations, make explicit reviewed requests instead of silently selecting every connected channel.

node --env-file=.env examples/schedule-video.mjs
# After reviewing the payload and platform options:
node --env-file=.env examples/schedule-video.mjs --publish

• Scheduling example source
• Publishing requirements

Poll status and read analytics

Save the returned post_id. The polling example makes at most 12 reads, spaced five seconds apart. It reports processing, failure, reported publication and timeout separately. A scheduled post may remain pending beyond the observation window.

The analytics example reads the selected project’s stored overview. Its output is private account data. The supplied code does not request synchronization, manufacture missing metrics or infer revenue attribution.

node --env-file=.env examples/poll-status.mjs --live-read
node --env-file=.env examples/read-analytics.mjs --live-read

• Polling logic and tests

Plan an editorial calendar

Use the free calendar builder for dates, topic rotation and timezone labels. Download a CSV and review it in a spreadsheet with an owner and status. It is an editorial worksheet, not a bulk-upload contract.

For assistant integrations, generate a local or hosted MCP template and replace the placeholder key in your client. First verify project and channel reads; inspect the tool schema before approving publishing.

• Build a content calendar
• Build an MCP configuration
• Adapter source and architecture