Socializioz MCP

Socializioz MCP connects supported AI clients to a real, authorized Socializioz workspace. The native remote MCP exposes the currently enabled Socializioz tool surface for authenticated workspace operations. Tool availability can evolve as capabilities are added, refined, or intentionally disabled; clients should rely on the tools returned by the live MCP connection rather than a fixed documentation count.

https://socializioz.com/api/mcp

The connection uses Socializioz authorization. Workspace membership, plan access, roles, connected-account capabilities, post state, approvals, media requirements, and publishing validation remain enforced.

What the connection unlocks

The value is not only the number of tools. A supported assistant can move through the complete workflow without losing workspace state:

Read context → Plan campaign → Create posts → Attach media → Validate → Approve → Schedule or publish → Verify result

For example, a user can ask an external assistant to create a launch campaign, prepare platform-specific posts, attach suitable workspace assets, send the work for approval, and then confirm the resulting Socializioz state.

Current access

Socializioz native MCP is currently available to Socializioz users at no additional cost during the current early-access period. This availability can change later as the product grows, but the documentation will be updated before any plan restriction is presented as active. Client-side availability can also depend on the AI provider’s plan, workspace settings, administrator controls, and support for remote MCP connections.

Connect a supported remote client

Open the client's connector settings

In ChatGPT, Claude, or another supported MCP client, open the area used to add remote tools or connectors.

Add the native endpoint

Use https://socializioz.com/api/mcp.

Authorize Socializioz

Choose the workspace

Select or confirm the workspace the client is allowed to operate.

Review requested access

Confirm the client identity and the categories of Socializioz actions being requested.

Test with a read action

Start by asking the client to identify the active workspace or list connected accounts before requesting a write or publishing action.

ChatGPT app and native MCP

Socializioz also has a published ChatGPT app.

Surface	Purpose
Published ChatGPT app	Use the currently approved Socializioz experience inside ChatGPT
Native remote MCP	Connect a supported remote MCP client to the current authenticated Socializioz tool surface
Docs MCP	Search and read public Socializioz documentation only

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

Open Socializioz in ChatGPT

Open the published Socializioz app in ChatGPT.

Claude

When remote connectors are available for your Claude account:

Open Settings.
Open Connectors.
Add the Socializioz remote MCP endpoint.
Complete Socializioz authorization.
Confirm the intended workspace.

Do not use an old local claude_desktop_config.json example as the primary setup method for the hosted Socializioz service.

Product MCP versus Docs MCP

Endpoint	Access
`https://socializioz.com/api/mcp`	Authenticated user workspace and actions
`https://docs.socializioz.com/mcp`	Public documentation search and reading only

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

Capability groups

Workspace and brand context

Read the authorized user’s profile, active workspace, available workspaces, brand context, subscription context, and supported capabilities. Representative tools include:

get_user_profile
get_workspace_context
get_brand_profile

Connected accounts

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

list_connected_accounts

Registered integration capabilities

integration_capability is the generic Socializioz boundary for registered connected integrations. It does not accept raw provider action IDs, credentials, or arbitrary proxy URLs. Use it in three stages:

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.

X live operations

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

MCP guidance and presentation

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.

get_mcp_help
render_socializioz_widget

Posts and drafts

Create and work with real Socializioz posts.

create_draft_post
list_posts
get_post
update_draft_post

Media assets

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 multipart upload_asset remains configured but intentionally disabled. It is not discoverable through the live MCP; use import_media_from_url for public HTTPS media or attach_assets_to_post when the MCP client actually supplies a file reference.

Campaigns

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

Approvals and review

Move posts through the authorized review workflow.

send_post_for_approval
approve_post
reject_post

Scheduling and publishing

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 discovery

list_user_workspaces

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.

Real workflow examples

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.

Review tomorrow’s queue

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.

Repair and retry a failed post

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.

Use workspace media

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.

Result verification

A client should claim success only when the returned Socializioz result confirms the action. After a write action, verify:

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.

Security model

MCP actions remain subject to:

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.

Current boundaries

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.

Troubleshooting

Problem	What to check
Authorization link fails or expires	Start the connection again from the MCP client and complete the new Socializioz authorization request.
Wrong workspace appears	Reconnect or reauthorize and explicitly select the intended workspace.
Tool returns unauthorized	Confirm the user, workspace membership, role, plan, and current client authorization.
Connected account is missing	Check the active workspace and Connections.
Write action does not complete	Read the returned error and verify the affected state inside Socializioz.
Schedule or publish is blocked	Check approval, media, destination requirements, timing, account health, and plan access.
Publish remains processing	Use `get_publish_status` and verify the final provider result before claiming it is live.
ChatGPT app has different tools	The published app and native MCP may be on different approved releases. Use the native endpoint for the current remote MCP surface.

Start

AI Agent

Operate

Engage and learn

Integrations

Workspace and team

Account

Reference

Help

Release notes

What the connection unlocks

Current access

Connect a supported remote client

ChatGPT app and native MCP

Open Socializioz in ChatGPT

Claude

Product MCP versus Docs MCP

Capability groups

Workspace and brand context

Connected accounts

Registered integration capabilities

X live operations

MCP guidance and presentation

Posts and drafts

Media assets

Campaigns

Approvals and review

Scheduling and publishing

Workspace discovery

Real workflow examples

Create a campaign and send it for approval

Review tomorrow’s queue

Repair and retry a failed post

Use workspace media

Result verification

Security model

Current boundaries

Troubleshooting

​What the connection unlocks

​Current access

​Connect a supported remote client

​ChatGPT app and native MCP

Open Socializioz in ChatGPT

​Claude

​Product MCP versus Docs MCP

​Capability groups

​Workspace and brand context

​Connected accounts

​Registered integration capabilities

​X live operations

​MCP guidance and presentation

​Posts and drafts

​Media assets

​Campaigns

​Approvals and review

​Scheduling and publishing

​Workspace discovery

​Real workflow examples

​Create a campaign and send it for approval

​Review tomorrow’s queue

​Repair and retry a failed post

​Use workspace media

​Result verification

​Security model

​Current boundaries

​Troubleshooting

​Related

What the connection unlocks

Current access

Connect a supported remote client

ChatGPT app and native MCP

Claude

Product MCP versus Docs MCP

Capability groups

Workspace and brand context

Connected accounts

Registered integration capabilities

X live operations

MCP guidance and presentation

Posts and drafts

Media assets

Campaigns

Approvals and review

Scheduling and publishing

Workspace discovery

Real workflow examples

Create a campaign and send it for approval

Review tomorrow’s queue

Repair and retry a failed post

Use workspace media

Result verification

Security model

Current boundaries

Troubleshooting

Related