How do I install the Ivx MCP Postiz Social skill?

Run npx skillmds@latest add intelli-verse-x/ivx-mcp-postiz-social in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ivx MCP Postiz Social safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ivx MCP Postiz Social?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ivx MCP Postiz Social free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ivx MCP Postiz Social?

intelli-verse-x (@intelli-verse-x) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ivx MCP Postiz Social by intelli-verse-x

Name: Ivx MCP Postiz Social
Rating: 4.2 (5 reviews)
Author: intelli-verse-x

Ivx MCP Postiz Social

Schedule and analyze social-media posts (Instagram, X, LinkedIn, TikTok) through the Postiz wrapper MCP — list channels, find free slots, create/schedule posts, pull analytics. Use for any "post this / what's scheduled / how did the post do" request.

intelli-verse-x Updated Sep 8, 2026 0 repo stars

File contents

Postiz — social scheduling

What it is

Postiz (https://postiz.intelli-verse-x.ai) is the org's social calendar: all connected accounts (Instagram, X, LinkedIn, TikTok, …) post from one place. Agents drive it through a stateless wrapper MCP with the Intelli Verse X org key baked in (Postiz's built-in MCP is deprecated — its in-memory sessions were racy across replicas).

Tile id: postiz (group "Talk to people")
MCP endpoint: https://postiz-mcp.intelli-verse-x.ai/
Auth: org key baked into the wrapper — no token needed. admin_call_mcp { tileId: "postiz" } just works.

Key tools (from the registry)

Tool	What it does
`postiz_list_integrations`	Connected social channels (get channel ids here first)
`postiz_list_posts`	Scheduled/published posts on the calendar
`postiz_find_slot`	Next free posting slot for a channel
`postiz_create_post`	Create/schedule a post (write)
`postiz_upload_from_url`	Attach media by URL
`postiz_analytics`	Post/channel performance

Worked example — "post our launch thread on X tomorrow morning"

postiz_list_integrations → find the X account's integration id.
postiz_find_slot for that channel around the requested time.
Draft the copy; if there's an image, postiz_upload_from_url first.
Show draft + channel + exact time and get approval — publishing is a write.
postiz_create_post { integrationId, content, publishDate, media }.
Confirm back with the scheduled time and the calendar entry; check postiz_analytics a day later if asked.

Common failure modes

401/403 — the baked org key was rotated; report it (secret postiz-mcp-secret / gateway admin-mcp-gateway-tokens) rather than asking the user for a key in chat.
Post created but never publishes — the target channel's OAuth to the social network expired; reconnect in the Postiz UI (portal tile postiz-studio). The MCP can't fix platform OAuth.
Wrong account posted — multiple integrations per platform exist; always resolve the integration id from postiz_list_integrations by name, never assume.
Media rejected — platform constraints (size/aspect/format) surface as create errors; re-encode and retry once, then escalate.

Cautions

Posts go out publicly under the org's brand — draft-then-approve every postiz_create_post, including "just reschedule it" edits. Never paste API keys into chat.

---name: ivx-mcp-postiz-socialdescription: Schedule and analyze social-media posts (Instagram, X, LinkedIn, TikTok) through the Postiz wrapper MCP — list channels, find free slots, create/schedule posts, pull analytics. Use for any "post this / what's scheduled / how did the post do" request.---# Postiz — social scheduling## What it isPostiz (`https://postiz.intelli-verse-x.ai`) is the org's social calendar:all connected accounts (Instagram, X, LinkedIn, TikTok, …) post from oneplace. Agents drive it through a **stateless wrapper MCP** with theIntelli Verse X org key baked in (Postiz's built-in MCP is deprecated —its in-memory sessions were racy across replicas).- Tile id: `postiz` (group "Talk to people")- MCP endpoint: `https://postiz-mcp.intelli-verse-x.ai/`- Auth: org key baked into the wrapper — no token needed. `admin_call_mcp { tileId: "postiz" }` just works.## Key tools (from the registry)| Tool | What it does ||---|---|| `postiz_list_integrations` | Connected social channels (get channel ids here first) || `postiz_list_posts` | Scheduled/published posts on the calendar || `postiz_find_slot` | Next free posting slot for a channel || `postiz_create_post` | Create/schedule a post (write) || `postiz_upload_from_url` | Attach media by URL || `postiz_analytics` | Post/channel performance |## Worked example — "post our launch thread on X tomorrow morning"1. `postiz_list_integrations` → find the X account's integration id.2. `postiz_find_slot` for that channel around the requested time.3. Draft the copy; if there's an image, `postiz_upload_from_url` first.4. **Show draft + channel + exact time and get approval** — publishing is a write.5. `postiz_create_post { integrationId, content, publishDate, media }`.6. Confirm back with the scheduled time and the calendar entry; check `postiz_analytics` a day later if asked.## Common failure modes- **401/403** — the baked org key was rotated; report it (secret `postiz-mcp-secret` / gateway `admin-mcp-gateway-tokens`) rather than asking the user for a key in chat.- **Post created but never publishes** — the target channel's OAuth to the social network expired; reconnect in the Postiz UI (portal tile `postiz-studio`). The MCP can't fix platform OAuth.- **Wrong account posted** — multiple integrations per platform exist; always resolve the integration id from `postiz_list_integrations` by name, never assume.- **Media rejected** — platform constraints (size/aspect/format) surface as create errors; re-encode and retry once, then escalate.## CautionsPosts go out publicly under the org's brand — draft-then-approve every`postiz_create_post`, including "just reschedule it" edits. Never pasteAPI keys into chat.

Frequently asked questions