Skip to main content
Glama
Sign In
reelfaceless-mcp

reelfaceless-mcp

by danyial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reelfaceless-mcp

MCP server (stdio) for the ReelFaceless public API. Schedule short-form video posts to YouTube and TikTok from Claude Desktop, Claude Code or any other MCP client.

Setup

You need an API key: ReelFaceless → workspace → Settings → API (Creator plan and up). Plan quotas and rate limits apply automatically.

Claude Code

claude mcp add reelfaceless \
  --env REELFACELESS_API_KEY=rf_your_key \
  -- npx -y reelfaceless-mcp@latest

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "reelfaceless": {
      "command": "npx",
      "args": ["-y", "reelfaceless-mcp@latest"],
      "env": { "REELFACELESS_API_KEY": "rf_your_key" }
    }
  }
}

Optional: REELFACELESS_BASE_URL to point at a different instance.

Related MCP server: viralnote-mcp

Tools

Tool

Purpose

list_channels

Connected channels incl. posting schedule (needed for channel IDs)

get_channel_info

TikTok posting constraints: allowed privacy levels, disabled interactions, max duration

upload_video

Upload a local MP4/MOV/WebM (max 500 MB), returns media_id

create_post

Schedule a post across channels — queue slots or a fixed time

list_posts

List posts, newest first, optional status filter

get_post_status

Per-channel status, remote URLs, error details

update_post

Edit a scheduled post: content, per-channel settings, timing, channels

publish_post_now

Publish a scheduled post immediately instead of waiting for its slot

get_post_metrics

Latest views/likes/comments per channel for a published post

Example prompt: "Upload ~/exports/recap.mp4 and add it to the queue for all my channels with the caption 'Weekly recap'."

Development

npm install
npm run build        # bundles to dist/index.js
npx tsx test/e2e.ts  # BASE=… RF_KEY=… VIDEO=… — full round-trip test

Available Tools

6 tools
create_postA

Create and schedule a video post across one or more channels. schedule_mode 'queue' assigns each channel its next free posting slot; 'custom' schedules all targets at scheduled_at (ISO 8601). Per-channel settings are optional and inherit from title/body. YouTube settings: title, description, privacy_status (public|unlisted|private), made_for_kids, contains_synthetic_media (AI disclosure), tags (string[]), category_id, default_language (BCP-47), notify_subscribers, embeddable, license (youtube|creativeCommon), public_stats_viewable. TikTok settings: caption, privacy_level (PUBLIC_TO_EVERYONE|MUTUAL_FOLLOW_FRIENDS|FOLLOWER_OF_CREATOR|SELF_ONLY), disable_comment, disable_duet, disable_stitch, video_cover_timestamp_ms, brand_organic_toggle, brand_content_toggle, is_aigc (AI label). Constraint: brand_content_toggle cannot be combined with SELF_ONLY.

Inputs: title (required), targets (required), media_id (required), schedule_mode (required), +2 more.

get_post_metricsA

Get the latest platform metrics (views, likes, comments) per channel for a published post, as of the last analytics sync.

Inputs: post_id (required).

get_post_statusB

Get a post with per-channel target status, scheduled/published times, remote URLs and error details.

Inputs: post_id (required).

list_channelsA

List the connected social channels (YouTube/TikTok) of the workspace, including each channel's posting schedule (weekday 0=Sunday…6=Saturday, time in the workspace timezone). Channel IDs are needed for create_post.

Inputs: no named parameters.

list_postsA

List posts of the workspace, newest first. Optional status filter (draft|scheduled|publishing|published|failed|canceled) matches posts with at least one target in that status.

Inputs: limit, status.

upload_videoA

Upload a local video file (MP4, MOV or WebM, max 500 MB) and return its media_id for create_post. Handles the presigned upload and verification.

Inputs: file_path (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: creating posts, retrieving metrics, fetching status, listing channels, listing posts, and uploading videos. No two tools overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_post, list_channels, upload_video). No mixing of conventions.

    Tool Count5/5

    With 6 tools, the set is well-scoped for managing video posts across channels. Each tool serves a clear role without unnecessary bloat or deficiency.

    Completeness3/5

    The tool set covers creation, status, metrics, and listing, but lacks update or delete operations for posts. Users cannot modify or remove existing posts, which is a notable gap for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers