Socializioz

The published ChatGPT app and native remote MCP are separate release surfaces. Their approved versions may not update at exactly the same time.

When remote connectors are available for your Claude account:
- OpenSettings.
- OpenConnectors.
- Add the Socializioz remote MCP endpoint.
- Complete Socializioz authorization.
- Confirm the intended workspace.

Do not use an old localclaude_desktop_config.jsonexample as the primary setup method for the hosted Socializioz service.

The Docs MCP cannot create campaigns, access private workspaces, modify posts, schedule content, or publish.

Read the authorized user's profile, active workspace, available workspaces, brand context, subscription context, and supported capabilities.

- get_user_profile
- get_workspace_context
- get_brand_profile

Inspect social accounts connected to the selected workspace, including available platform and health information.

integration_capabilityis the generic Socializioz boundary for registered connected integrations. It does not accept raw provider action IDs, credentials, or arbitrary proxy URLs.
- list_connections— discover authorized integration connections available to the selected workspace.
- list_capabilities— inspect only the Socializioz-registered capabilities for one returned connection.
- run— execute a returned registered capability within its current policy boundary.

Read capabilities can run through this gateway when authorized. Social publishing writes still use the normal Socializioz Post lifecycle rather than bypassing it through an integration action. Other external writes can require a single-use confirmation token created by the authenticated Socializioz UI; the MCP tool cannot mint that confirmation itself.

The presence of a provider adapter in internal source does not mean that provider is publicly available. Clients should use only connections and capabilities actually returned for the authorized user/workspace.

Use the verified connected X account boundary for live reads and explicit provider actions.

- x_live_read
- x_send_dm— only when the user explicitly asks to send a DM
- x_delete_post— only when the user explicitly asks to delete an X post

Use MCP-specific help when deeper operating rules are needed, and render a compact Socializioz control card from an existing tool result without changing data.

Create and work with real Socializioz posts.

- create_draft_post
- list_posts
- get_post
- update_draft_post

Use the workspace Media Library and prepare media for destinations.

- list_workspace_assets
- get_asset
- import_media_from_url
- create_workspace_asset
- probe_media_url
- media_preflight
- attach_assets_to_post
- detach_assets_from_post
- reorder_attached_assets
- replace_attached_assets

Legacy multipartupload_assetremains configured but intentionally disabled. It is not discoverable through the live MCP; useimport_media_from_urlfor public HTTPS media orattach_assets_to_postwhen the MCP client actually supplies a file reference.

Create, organize, and analyze campaigns and content plans.

- list_campaigns
- create_campaign
- update_campaign
- analyze_campaign
- list_campaign_plan_items
- create_campaign_plan_item
- update_campaign_plan_item
- convert_plan_item_to_post

Move posts through the authorized review workflow.

- send_post_for_approval
- approve_post
- reject_post

Operate the post after content, media, destination, and approval checks are satisfied.

- schedule_post
- reschedule_post
- cancel_scheduled_post
- publish_now
- retry_failed_publication
- get_publish_status
- get_recommended_posting_time

Workspace invitation and leave operations are intentionally disabled in the current remote MCP surface. Manage those actions in Socializioz rather than assuming they are available to an MCP client.

Create a campaign and send it for approval

Use the active brand and workspace. Create a seven-day launch campaign for our new product across Instagram, LinkedIn, and TikTok. Build the content plan, create three platform-specific draft posts, attach suitable approved assets, validate the destinations, and send the posts for approval. Do not publish.

List tomorrow's scheduled posts. Identify anything missing required media, waiting for approval, targeting an unhealthy account, or showing a previous publishing failure. Do not change anything yet.

Read the failed post and its current publish status. Explain the returned failure, verify that the issue is resolved, then retry publishing only if the post is still valid and authorized.

Find the approved vertical product video in the workspace assets, attach it to the TikTok draft, run media preflight, and show me the updated post state.

A client should claim success only when the returned Socializioz result confirms the action.

- The correct workspace was used.
- The correct record was affected.
- The returned post, campaign, asset, approval, or publication state matches the request.
- A provider-side publish is not described as live while it is still processing.
- A failed or unauthorized action is not rewritten as success.

The affected item should also be visible in the appropriate Socializioz interface.

- Socializioz authentication.
- User-authorized client access.
- Workspace membership and selected workspace scope.
- Role and administrative permissions.
- Plan and feature availability.
- Connected-account ownership and health.
- Provider permissions and account capabilities.
- Post-state and approval validation.
- Media and destination requirements.
- Publishing and retry rules.

The MCP does not provide a tool that grants cross-customer access or silently bypasses these controls.

- Native MCP tools operate the existing Socializioz workflow; they do not unlock unsupported plans or provider capabilities.
- Image and video generation availability can differ from media upload, import, and attachment tools.
- External clients should not be given access tokens manually.
- Provider publishing can remain in a processing state after Socializioz accepts the request.
- The published ChatGPT app can follow a separate review and rollout schedule from the native MCP.

- How Socializioz works
- Socializioz Agent
- Integrations
- Connections
- Campaigns
- Approvals
- Publishing Hub
- Security

Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.

Schedule and publish social media posts across 13+ platforms, manage your content calendar, and generate AI-powered captions through any MCP-compatible AI assistant.

Streamline your social media with Postiz. Schedule posts, analyze performance, and manage all accounts in one place

Draft, schedule and publish social posts to LinkedIn, X, Instagram, Facebook, Threads, TikTok, Pinterest and YouTube from your AI assistant, in a brand voice learned per account.

Schedule, generate and publish social posts to X, LinkedIn, Instagram, Threads and YouTube from any MCP client.

Create, schedule, and publish social media posts to 9 platforms from Claude, Cursor, or any AI agent. Hosted server with OAuth or API key auth.

Groniz — Social Media Connector for AI Agents

Groniz is a remote MCP server that lets AI agents publish and schedule social content across 32+ networks, including X, Instagram, LinkedIn, Facebook, Threads, TikTok, YouTube, Reddit, Pinterest, Bluesky, Mastodon, Telegram, and Discord. It provides a unified interface for managing connected accounts, authentication, platform-specific formatting, and content delivery.

Live TikTok creator intelligence MCP — 7 tools (analyze creators, score hooks, remix scripts, predict virality) that chain automatically via a recommended_chain that pre-fills the next 3 tool calls.

The most flexible and fun way to grow on social: a strategist, ghostwriter, scheduler and analyst in one — inside the AI you already use, so it has all your context: your real work, in your voice. Starting with LinkedIn, X and Substack.

Social media analytics for Instagram, TikTok, X, Facebook, LinkedIn and Threads.