このMCPでできること
Schedules, drafts, publishes, manages, and analyzes branded social media posts across connected platforms.
機能
ツール
21
ツール
campaign_summary
Per-brand campaign rollup (brands are ViralCat's campaign unit): posted/scheduled/failed/draft counts, platforms used, next scheduled date, last posted date, and auto-post settings. Optionally scope to one brand_id.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'brand_id': {'type': 'string', 'format': 'uuid', 'pattern': '^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$'}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
cancel_post
WRITE (safe): cancel a queued post, or move it to a new slot. Omit scheduled_date to CANCEL (status -> cancelled; the publisher ignores it). Pass scheduled_date to RESCHEDULE to that time instead (ISO 8601, at least 15 minutes out; a draft keeps its draft status). Works on draft or scheduled posts (cancel or reschedule); also works on FAILED posts but cancel-only (omit scheduled_date) â this is the way to clear a dead failed-post backlog, since failed has no other exit. Posts already posting/posted/cancelled are immutable. Get post ids from content_queue, list_posts or diagnose_failures.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['post_id'], 'properties': {'post_id': {'type': 'integer', 'maximum': 9007199254740991, 'minimum': -9007199254740991, 'description': 'Post id to cancel or reschedule (from content_queue)'}, 'scheduled_date': {'type': 'string', 'description': 'Omit to cancel. Provide to reschedule: ISO 8601, at least 15 minutes in the future'}}}
content_queue
The forward content pipeline: drafts awaiting approval first, then scheduled posts in publish order. Use to review what is queued before it goes out, and to find draft ids for schedule_post.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'integer', 'default': 50, 'maximum': 100, 'minimum': 1}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
create_brand
WRITE (gated): create a brand (content profile) so create_draft and schedule_post have something to target. Every other write here needs a brand_id, so an agent had no way to set one up. Returns the brand_id and the Drive folder the publisher will read its media from (Viral-Cat/_Res/{name}/Vids). Publishes nothing and reaches no audience.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['name'], 'properties': {'name': {'type': 'string', 'maxLength': 100, 'minLength': 1, 'description': 'Brand name. Also names its Drive media folder, so keep it filesystem-friendly.'}, 'cta_url': {'type': 'string', 'maxLength': 500, 'description': 'Link included in posts.'}, 'hashtags': {'type': 'array', 'items': {'type': 'string', 'maxLength': 100}, 'maxItems': 30, 'description': 'Brand hashtags appended to captions unless skip_hashtags is set.'}, 'description': {'type': 'string', 'maxLength': 1000}, 'website_url': {'type': 'string', 'maxLength': 500}, 'content_type': {'enum': ['video', 'image'], 'type': 'string', 'description': 'What the publisher should expect to find for this brand.'}}}
create_draft
WRITE (safe): create a DRAFT post for a brand. Drafts are never picked up by the publisher, so nothing goes live; a human approves in the dashboard or promotes it later with schedule_post. scheduled_date is a proposed slot (default: 7 days out).
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['brand_id', 'platform'], 'properties': {'caption': {'type': 'string', 'maxLength': 2200, 'description': "Post body. Omit to inherit the brand's taglines."}, 'brand_id': {'type': 'string', 'format': 'uuid', 'pattern': '^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$'}, 'platform': {'type': 'string', 'maxLength': 20, 'description': 'Target platform, e.g. youtube, tiktok, instagram'}, 'reply_text': {'type': 'string', 'maxLength': 2200, 'description': "Follow-up reply posted under the main post. On X this is where a link belongs: a URL in the post body costs up to 94% of the reach (near-total on a non-Premium account), while the same URL one reply down costs nothing. Omit to reply with the brand's CTA url; pass an empty string for no reply at all. Ignored by every platform except X."}, 'skip_hashtags': {'type': 'boolean', 'description': "true = publish the caption as-is with NO brand hashtags appended; false = always append them. Omit to auto-detect: long hand-authored captions (>280 chars, no '#') skip hashtags. The result's hashtagsSkipped shows the decision."}, 'scheduled_date': {'type': 'string', 'description': 'Proposed ISO 8601 slot, e.g. 2026-07-15T09:00:00Z'}}}
create_media_upload
WRITE (gated): open a Google Drive upload session for media you hold locally, so a clip rendered on your own machine never has to be published publicly just so ViralCat can fetch it back. Returns an uploadUrl - PUT the bytes to it yourself (no auth header) and Drive stores the file; the response Location/id is the fileId for create_draft or schedule_post. When brand is given the file lands in the folder the generator actually reads for that media type: Viral-Cat/_Res/{brand}/Imgs for an image, Vids for a video, Music for audio. Without brand it defaults to the Viral-Cat folder. Video, image or audio up to 100MB. Publishes nothing and reaches no audience.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['file_name', 'mime_type', 'size_bytes'], 'properties': {'kind': {'enum': ['video', 'image', 'music'], 'type': 'string', 'description': 'Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right.'}, 'brand': {'type': 'string', 'maxLength': 200, 'description': 'Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given.'}, 'file_name': {'type': 'string', 'maxLength': 200, 'description': 'Name to save as in Drive, e.g. "ducktax-short.mp4".'}, 'folder_id': {'type': 'string', 'maxLength': 200, 'description': 'Destination Drive folder id, overriding brand.'}, 'mime_type': {'type': 'string', 'maxLength': 100, 'description': 'Media type of the file, e.g. "video/mp4".'}, 'size_bytes': {'type': 'integer', 'maximum': 9007199254740991, 'description': 'Exact byte length of the file. Drive rejects a mismatch.', 'exclusiveMinimum': 0}}}
diagnose_failures
Group failed posts by platform + normalized failure reason: counts, date range, affected brands, a sample raw error, a recoverable flag (retry_failed_posts can re-queue it) and a concrete suggested fix per group. Answers "what is broken and why" in one call. Read-only.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'days': {'type': 'integer', 'default': 60, 'maximum': 365, 'minimum': 1, 'description': 'Rolling window of failed posts to analyze'}, 'platform': {'type': 'string', 'maxLength': 20, 'description': 'Scope to a single platform, e.g. pinterest'}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
get_brand_details
Full content profile for one brand: description, taglines, hashtags, CTA/website URL, niche (category/subcategory), content type, target platforms, and active discount. Use this to write on-brand captions BEFORE calling create_draft or schedule_post. Read-only; returns no secrets.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['brand_id'], 'properties': {'brand_id': {'type': 'string', 'format': 'uuid', 'pattern': '^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$'}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
get_pipeline_summary
High-level snapshot of the posting pipeline: active brand count, a status breakdown (how many scheduled/posted/failed/etc.), a per-platform breakdown, how many posts are due in the next 7 days, and the next scheduled date. Use for 'how's the pipeline?' style questions.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
list_brands
List brands (content profiles), newest first, with per-brand post counts (posted/scheduled) and the next scheduled date. Use to see which brands exist and how active each is. Excludes archived brands. Returns `total` (all active brands) next to `count` (rows returned): when `truncated` is true the roster was cut off by `limit`, so raise it (max 50) before concluding a brand does not exist.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'integer', 'default': 20, 'maximum': 50, 'minimum': 1}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
list_connections
List connected platform accounts (channels) and their health: platform, account username, connected flag, posting-enabled flag, and token expiry. Use to check which platforms are wired up and whether any connection has expired. Never returns access or refresh tokens.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
list_posts
List posts across all platforms, newest scheduled first. Each row is one publication on one platform. Filter by status (draft|scheduled|posting|posted|failed|cancelled) and/or platform (youtube|tiktok|instagram|...). Returns caption, brand name, permalink, error message when present, and publishWarning for posts that succeeded with an anomaly (e.g. published without media).
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'integer', 'default': 20, 'maximum': 50, 'minimum': 1}, 'status': {'enum': ['draft', 'scheduled', 'posting', 'posted', 'failed', 'cancelled'], 'type': 'string'}, 'platform': {'type': 'string', 'maxLength': 20, 'description': 'Filter to a single platform, e.g. youtube or tiktok'}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
post_performance
Publish-outcome metrics over a rolling window (default 30 days): posted/failed/cancelled totals, success rate, per-platform breakdown, and the most recent published posts with permalinks plus their latest stored engagement snapshot (views/likes/comments/shares; available for youtube/tiktok/twitter/threads). Snapshots are stored, not live: call refresh_post_metrics first if the numbers must be current. Optionally scope by brand_id and/or platform.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'days': {'type': 'integer', 'default': 30, 'maximum': 365, 'minimum': 1}, 'brand_id': {'type': 'string', 'format': 'uuid', 'pattern': '^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$'}, 'platform': {'type': 'string', 'maxLength': 20}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
preflight_check
READ-ONLY: validate a post BEFORE it is scheduled or published, so a problem is caught up front instead of discovered as a failure afterwards. Checks the exact things that produced the failed-post backlog: incompatible media for the platform (e.g. video to Pinterest), a disconnected or unrefreshable platform token (LinkedIn has no refresh token on this API tier and needs a manual browser reconnect roughly every 60 days â that's an expected state, not a bug), Facebook posting to an account with no Page (impossible via the Graph API), content referencing an already-passed date/season/promo code, and X/Twitter free-tier monthly write-cap headroom. Pass post_id to check one existing post; omit it to scan the forward queue (draft + scheduled, soonest first) and return only posts that have at least one issue.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'integer', 'default': 20, 'maximum': 50, 'minimum': 1, 'description': 'Queue-scan mode only: how many upcoming posts to check.'}, 'post_id': {'type': 'integer', 'maximum': 9007199254740991, 'minimum': -9007199254740991, 'description': 'Check one existing post (id from list_posts or content_queue). Omit to scan the whole upcoming queue instead.'}, 'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users (email contains "sample"). Default: real data only.'}}}
reconnect_platform
WRITE (safe): attempt a server-side token refresh for a platform whose access token has lapsed, updating the stored connection's token/expiry. Works without a browser when a refresh token is on file (twitter/youtube/google_drive self-heal this way); returns needsManualReauth + a dashboard link when the platform genuinely requires a manual browser reconnect (e.g. threads). Cannot publish or touch content, only refreshes credentials; safe to retry. Never exposes tokens.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['platform'], 'properties': {'platform': {'type': 'string', 'maxLength': 20, 'description': 'Platform to reconnect, e.g. twitter, youtube, google_drive'}}}
refresh_post_metrics
WRITE (gated): fetch current engagement (views/likes/comments/shares) for already-published posts and store today's snapshot, then read it back with post_performance. This is the only way to update the numbers without opening the dashboard Stats tab. Supported platforms: youtube, tiktok, twitter, threads; LinkedIn and the rest expose no engagement API. A 60-minute cooldown applies per account and protects X's free-tier read quota, so a call inside it returns skipped:true and changes nothing. Publishes nothing and reaches no audience.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'include_samples': {'type': 'boolean', 'default': False, 'description': 'Include sample users. Default false: real accounts only, matching every read tool.'}}}
reschedule_post
WRITE (gated): move ONE post to a new future slot (ISO 8601, at least 15 minutes out). Unlike cancel_post this also accepts FAILED posts: a failed post is re-queued (status -> scheduled, error cleared). Draft and scheduled posts keep their status. Refuses posts that would structurally fail again (archived brand, incompatible media, Facebook with no Page).
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['post_id', 'scheduled_date'], 'properties': {'post_id': {'type': 'integer', 'maximum': 9007199254740991, 'minimum': -9007199254740991, 'description': 'Post id (from list_posts, content_queue or diagnose_failures)'}, 'scheduled_date': {'type': 'string', 'description': 'New slot, ISO 8601, at least 15 minutes in the future'}}}
retry_failed_posts
WRITE (gated): bulk re-queue recoverable failed posts (default reason classes: token_expired, missed_window, platform_transient_error, drive_media_missing). dry_run DEFAULTS TO TRUE and only returns the plan; pass dry_run=false to actually reschedule. Retries are staggered per platform (spacing_minutes apart) and capped at limit, so a bulk retry cannot dogpile a platform API. Posts that would structurally fail again (archived brand, incompatible media, Facebook with no Page) are skipped with the reason. Use diagnose_failures first to see what is recoverable.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'integer', 'default': 20, 'maximum': 50, 'minimum': 1}, 'dry_run': {'type': 'boolean', 'default': True, 'description': 'true = plan only, change nothing (the default)'}, 'reasons': {'type': 'array', 'items': {'type': 'string', 'maxLength': 40}, 'description': 'Failure reason classes to retry. Default: token_expired, missed_window, platform_transient_error, drive_media_missing. Non-retryable classes are rejected.'}, 'platform': {'type': 'string', 'maxLength': 20, 'description': 'Scope to a single platform'}, 'start_at': {'type': 'string', 'description': 'ISO 8601 start of the retry window, at least 15 minutes out. Default: ~20 minutes from now.'}, 'spacing_minutes': {'type': 'integer', 'default': 30, 'maximum': 240, 'minimum': 5, 'description': 'Gap between retries on the same platform'}}}
schedule_post
WRITE (gated): queue a post for FUTURE publishing, at least 15 minutes out (immediate posting is not available over MCP). Either pass post_id to promote an existing draft, or brand_id + platform to create a new scheduled post. The publishing cron sends it at the scheduled time.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['scheduled_date'], 'properties': {'caption': {'type': 'string', 'maxLength': 2200}, 'post_id': {'type': 'integer', 'maximum': 9007199254740991, 'minimum': -9007199254740991, 'description': 'Draft post id to promote (from content_queue)'}, 'brand_id': {'type': 'string', 'format': 'uuid', 'pattern': '^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$'}, 'platform': {'type': 'string', 'maxLength': 20}, 'reply_text': {'type': 'string', 'maxLength': 2200, 'description': "Follow-up reply posted under the main post. On X this is where a link belongs: a URL in the post body costs up to 94% of the reach (near-total on a non-Premium account), while the same URL one reply down costs nothing. Omit to reply with the brand's CTA url; pass an empty string for no reply at all. Ignored by every platform except X."}, 'skip_hashtags': {'type': 'boolean', 'description': "true = publish the caption as-is with NO brand hashtags appended; false = always append them. Omit to auto-detect: long hand-authored captions (>280 chars, no '#') skip hashtags. When promoting a draft without a new caption, omitting this keeps the draft's existing setting."}, 'scheduled_date': {'type': 'string', 'description': 'ISO 8601, at least 15 minutes in the future'}}}
update_brand
WRITE (gated): correct a brand's content profile: description, taglines, hashtags, CTA and website links, content type, and the auto-post switch. This is the repair path for a brand carrying wrong copy, which otherwise makes every caption for it wrong, and the off switch for a brand whose generator is posting against your content rules. Only the fields you pass change; the rest keep their stored values. Cannot rename a brand (the name also names its Drive media folder) and cannot touch posting frequency/day or discount settings. Queues nothing and publishes nothing itself.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['brand_id'], 'properties': {'cta_url': {'type': 'string', 'maxLength': 500, 'description': 'Link included in posts. Pass an empty string to clear it.'}, 'brand_id': {'type': 'string', 'format': 'uuid', 'pattern': '^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$'}, 'hashtags': {'type': 'array', 'items': {'type': 'string', 'maxLength': 100}, 'maxItems': 30, 'description': 'Brand hashtags appended to captions unless skip_hashtags is set.'}, 'taglines': {'type': 'array', 'items': {'type': 'string', 'maxLength': 500}, 'maxItems': 30, 'description': 'Short lines the publisher rotates through when a post has no caption of its own.'}, 'description': {'type': 'string', 'maxLength': 1000, 'description': 'What the product actually is. The generator writes captions from this, so a wrong description makes every post wrong.'}, 'website_url': {'type': 'string', 'maxLength': 500}, 'content_type': {'enum': ['video', 'image'], 'type': 'string', 'description': 'What the publisher should expect to find for this brand.'}, 'auto_post_enabled': {'type': 'boolean', 'description': 'false = stop the content generator booking posts for this brand from its next cycle; true = let it resume. This is the only way to stop a brand auto-posting without opening the dashboard. Already-scheduled posts are NOT withdrawn by this: cancel those with cancel_post.'}}}
upload_media
WRITE (gated): fetch a public media URL and store it in the connected Google Drive, returning the Drive fileId to pass to create_draft or schedule_post. This uploads to YOUR OWN Drive; it publishes nothing and reaches no audience. Accepts video, image or audio up to 100MB. With brand, files land in the folder the generator actually reads for that media type: Viral-Cat/_Res/{brand}/Imgs for an image, Vids for a video, Music for audio. Without brand it defaults to the Viral-Cat folder, and folder_id overrides both.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['source_url'], 'properties': {'kind': {'enum': ['video', 'image', 'music'], 'type': 'string', 'description': 'Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right.'}, 'brand': {'type': 'string', 'maxLength': 200, 'description': 'Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given.'}, 'file_name': {'type': 'string', 'maxLength': 200, 'description': 'Name to save as. Omit to take it from the URL.'}, 'folder_id': {'type': 'string', 'maxLength': 200, 'description': 'Destination Drive folder id, overriding brand. Omit to use the Viral-Cat folder.'}, 'source_url': {'type': 'string', 'format': 'uri', 'description': 'Public https URL of the media to store, e.g. a rendered Short. Must be reachable without auth.'}}}
履歴
最近のツール変更
追加
update_brand
2026年9月29日2:47
追加
create_brand
2026年9月29日2:47
追加
create_media_upload
2026年9月29日2:47
追加
upload_media
2026年9月29日2:47
追加
reconnect_platform
2026年9月29日2:47
追加
refresh_post_metrics
2026年9月29日2:47
追加
reschedule_post
2026年9月29日2:47
追加
retry_failed_posts
2026年9月29日2:47
追加
cancel_post
2026年9月29日2:47
追加
schedule_post
2026年9月29日2:47
追加
create_draft
2026年9月29日2:47
追加
preflight_check
2026年9月29日2:47
追加
diagnose_failures
2026年9月29日2:47
追加
campaign_summary
2026年9月29日2:47
追加
content_queue
2026年9月29日2:47
追加
post_performance
2026年9月29日2:47
追加
list_connections
2026年9月29日2:47
追加
get_pipeline_summary
2026年9月29日2:47
追加
list_posts
2026年9月29日2:47
追加
get_brand_details
2026年9月29日2:47
追加
list_brands
2026年9月29日2:47
関連MCP
類似のMCPサーバー
captapi
io.github.CDCStream/captapi
Retrieves social media profiles, posts, engagement metrics, comments, marketplace listings, events, and Meta advertising data acr…
SendIt
io.github.Shree-git/sendit
Plans, generates, approves, schedules, publishes, and analyzes social media content across LinkedIn, Instagram, Threads, TikTok, …
aidelly
io.github.wilzer/aidelly
Supports agency social media operations including content creation, approvals, scheduling, publishing, repurposing, analytics, ec…
LinkedIn MCP Server (Salesbot)
cz.salesbot/linkedin-mcp-server
Supports LinkedIn lead discovery, contact enrichment, CRM pipelines, campaign sequencing, message approval and human-reviewed out…
excalibur-mcp
io.github.lonniev/excalibur-mcp
Creates, schedules, manages, and measures formatted posts for X, with OAuth, snippets, writing voice, and post performance tracki…
uplika
com.uplika/uplika
Publishes and manages posts, replies, messages, media, and automations across connected social platforms.
Prowlo — Reddit & X for AI agents
com.prowlo/reddit-x
Indexes and searches Reddit and X-related social data, discovers communities, monitors keywords, finds engagement opportunities, …
ChiefLab
io.github.bdentech/chieflab
Runs approval-gated product launch workflows with channel-specific marketing drafts, social publishing, email actions, measuremen…