MCP.so
登录
J

JuzPost MCP Server

@JuzPost

基本信息

传输方式

streamable-http

认证方式

无需认证

分类

其他

作者

JuzPost

关于 JuzPost MCP Server

Draft, schedule and publish social media posts from Claude, ChatGPT, Cursor or any MCP client. Write a post once, attach images or video, pick accounts and schedule or publish to 11 networks: X, LinkedIn, Instagram, Facebook, TikTok, YouTube, Threads, Bluesky, Pinterest, Tumblr and WordPress. Tools check each platform's caption, media and format limits before posting, list the queue, and edit, reschedule or delete posts. Tools: get_context, list_workspaces, switch_workspace, list_accounts, list_groups, list_options, get_platform_limits, create_upload_url, upload_media, upload_file, create_post, schedule_post, update_post, get_post, list_posts, delete_post. Pricing: the MCP server, REST API and CLI are on paid plans from Solo ($19/mo, 7-day trial). A free scheduler plan (2 accounts, 15 queued posts, no X) exists in the web app but does not include MCP access.

连接信息

https://www.juzpost.com/mcp

接入方式

claude mcp add juzpost --transport http https://www.juzpost.com/mcp

JuzPost MCP Server 工具

19

Reports who this connection is, the one workspace it acts on (use switch_workspace to change it), the plan, billing state, entitlements, quotas, limits and a plain-language list of what is blocked right now. Use this to see what the connection can do, and after an error mentions a plan or quota. Returns user, credential, workspace, plan, billing, entitlements, quotas, limits and blocked[]. The plan and quotas.subscription belong to the subscription of the workspace owner (ownedBy says whether that is the user) and are counted across every workspace that owner has; quotas.workspace is this workspace alone. Say which is which when reporting numbers. workspace.timezone is null until the user picks a plan on the website. Does NOT change anything. Works on every plan, including a workspace with no plan.

Lists every workspace the user belongs to, marks the one this connection acts on, and says what each allows through the connector: none (Free or no plan) or full (Solo, Growth, Pro). Use this when the user names another workspace or a tool reports a plan lock; then switch_workspace moves the connection. Returns workspaces[] (id, name, slug, isOwner, current, plan, access). Does NOT switch, create or change any workspace.

A connection acts on one workspace at a time. This moves it onto another workspace the user belongs to (id or slug from list_workspaces) for every later call, until switched again, and returns the new context. Use this when the user names a workspace other than the current one; confirm with them before switching. Returns switched and the full get_context shape for the new workspace, which says what that workspace's plan allows. Does NOT create workspaces and does NOT touch posts or accounts.

Lists the social accounts connected to the workspace, with health, how many posts are queued on each, and the effective limits for that account. Use this to pick the accounts for create_post and schedule_post, or to check whether an account needs reconnecting. Returns accounts[] (id, ref, platform, username, health, scheduledCount, limits, blockedByPlan, and seo for WordPress accounts), nextCursor and hasMore. seo is "yoast" when the WordPress site lets this account write Yoast SEO fields (schedule_post wordpress.seo), and "core" when it does not. health.status is the same as the dashboard: an expired access token that renews itself is still active; only needs_reconnect means the user must reconnect. ref is the account as "platform:handle" (e.g. "x:acme_studio"): pass it wherever a tool takes an account, since it is what the person reads when approving; it is null when the account has no handle, and then the id is used. Does NOT connect or disconnect accounts; that happens in the dashboard.

Lists the choices one account offers for a setting the schedule needs, read live from the platform. Requests: list_board (pinterest, ids go in pinterest.board_id); list_post_type (wordpress, ids go in wordpress.post_type). Use this when the user posts to Pinterest: list the boards, ask which one, and pass its id as board_id. Use list_post_type when the user wants a WordPress post published as something other than a blog post (a short story, a page): pass the matching id as post_type; the name lists the taxonomies that type takes in terms. Returns field (where the ids go) and choices[] with id and name. Refer to a choice by its name when talking to the user. Does NOT change anything.

Returns the full publishing rules for one platform or all of them: caption and title limits and units, media counts, sizes, formats, whether media is required, hashtags, mentions, native scheduling, plus the global file rules. Use this before drafting to answer "will this fit on X / Instagram / TikTok". Returns platforms[] (one object per platform, with effectiveBodyLimit) and global. imageFormats is what the post may carry: a PNG or WebP is converted to JPEG for a platform that only takes JPEG, and a still image over maxImageBytes is compressed under it when it publishes, so neither blocks. Does NOT look at a specific account; list_accounts carries the per-account effective limits.

Lists channel groups (named sets of accounts) with their member account ids. Use this when the user names a group ("post to my brand accounts") to resolve it to the account ids schedule_post takes. Returns groups[] (id, name, accountIds, accountCount), nextCursor and hasMore. Does NOT create or edit groups.

Lists posts in the workspace: drafts, scheduled, published and failed. Use this to find drafts to schedule, to review the queue, or to find a post id for get_post, update_post, schedule_post (publish_now on a scheduled post) or delete_post (any status). Returns posts[] (id, status, type, title, content, mediaUrls, scheduledFor), nextCursor and hasMore. Refer to posts by title or caption when talking to the user; ids are for tool calls. Does NOT include per-account results; call get_post for those.

Fetches one post with its per-account rows: status, publish time, published time and any error per account. Use this after schedule_post to confirm what happened, or when the user asks why a post failed. Returns the post (content, media, metadata, socialAccountIds) and targets[] with platform and username. Refer to posts by title or caption and to accounts by platform and username when talking to the user; ids are for tool calls. Does NOT retry or change the post.

Creates a draft post with everything the composer saves: caption, title, description, hashtags, media, the accounts it goes to, per-account text (account_overrides, channel_overrides), per-account media and covers, and each platform's settings. Media can be public URLs (downloaded and stored server-side) or media keys from upload_media. Facebook text post with a link: also set platform_settings.facebook.link (see that field) so Facebook shows a preview card. Use this only once you have the full brief from the user: the post type, the text, and the media if the type needs it. `type` is required and is never guessed: use the type the user stated (text, image, video, story or blog); if they did not say, ask them before calling this tool. A story is an Instagram or Facebook Story: one image or one video, no caption on Instagram. A blog post goes to WordPress: title is required and becomes the page heading. Put the body in description, as HTML; it is sent exactly as written. Plain text also works: blank lines become paragraphs. WordPress keeps p, br, hr, h2 to h6 (with id), ul, ol, li, blockquote, strong, em, a (href, rel, target, title), code, pre, abbr, time, figure, figcaption, the table tags and img (src, alt, width, height). Do not use h1 (the title is already the page heading), script or style (WordPress removes the tag but leaves its text visible). The first image is the featured image; any others are added under the body in order. Images only, no video. Then schedule_post puts the draft on the calendar. To schedule straight away, call schedule_post with the content instead: it creates and schedules in one call. Pass the same idempotency_key on a retry so a network error never makes two drafts. Returns the draft (post) plus warnings[] naming any platform whose caption limit the content exceeds, and created=false when the idempotency_key matched an existing draft. Does NOT schedule or publish anything.

Edits a draft or a scheduled post, the same edit the composer makes: caption, title, description, hashtags, type, media keys, cover, accounts, per-account text, media and covers, platform settings, and the time. Only the fields passed change; media_keys: null clears the media. The per-account maps (account_overrides, channel_overrides, media_by_account, cover_by_account, each platform's settings) change only the accounts they name: send just the accounts you are changing, and every other account keeps its text, media and settings. An account's entry is its whole text or settings; account_overrides: { id: null } clears that account's text. account_ids is the complete list: an account left out is removed from the post. Facebook text post with a link: also set platform_settings.facebook.link (see that field) so Facebook shows a preview card. A scheduled post is checked the way schedule_post checks one, and nothing is written when it is refused. It can no longer be edited from 10 minutes before its first account fires, or once an account has started preparing (an Instagram or Pinterest video prepares earlier). publish_at on a scheduled post moves it; on a draft it is the time the draft keeps. Times are ISO 8601 ending in Z or an offset, like 2026-11-03T09:00:00+05:30: use the user's own local time with its offset. workspace.timezone from get_context is the workspace's display zone, not necessarily where the user is; if you are unsure of their timezone, ask them. Use this when the user revises a post before it goes out. Returns the updated post and warnings[] for any platform caption limit the new content exceeds. Does NOT edit published or failed posts (returns an error), and does NOT ingest URLs; use upload_media first.

Permanently deletes a post in any status (draft, scheduled, failed or published) from JuzPost, with its per-account rows. A scheduled post's timer is cancelled first, so it never publishes; a published post's analytics in JuzPost go with it. Use this only when the user explicitly asks to delete the post. Returns deleted=true, the post id and what the deleted post was (title, caption, type, media count). Does NOT remove anything already published on a platform: the post stays there and has to be deleted on the platform itself.

Schedules a post to one or more accounts at publish_at, or publishes immediately with publish_now=true. This publishes to real accounts. Times are ISO 8601 ending in Z or an offset, like 2026-11-03T09:00:00+05:30: use the user's own local time with its offset. workspace.timezone from get_context is the workspace's display zone, not necessarily where the user is; if you are unsure of their timezone, ask them. Facebook text post with a link: also set platform_settings.facebook.link (see that field) so Facebook shows a preview card. One call does it all: without post_id it creates the post from the content and settings given and schedules it; with post_id it schedules that draft, applying any fields sent first. type story is an Instagram or Facebook Story: one image or one video, no caption on Instagram. With the post_id of a post that is already scheduled and publish_now=true, it publishes that post now instead of at its time, after the same checks a post published now faces: a refused check leaves it scheduled as it was, and a post under 10 minutes from its time is refused. To change a scheduled post's content or time, use update_post. It takes everything the composer can set: caption, title, media, accounts, per-account text (account_overrides, channel_overrides), per-account media and covers, per-account times, and each platform's settings. With post_id, the per-account maps change only the accounts they name, as in update_post: every other account keeps what the draft has. account_ids is the complete list: an account left out is removed. Each platform setting says whether it is required, an account default or optional; a Pinterest account needs pinterest.board_id, from list_options. Every problem on every account is refused in one error, before anything is armed. Use this only after the user has confirmed the content, the accounts and the time. A refused call writes nothing: no draft is created and no draft is changed. Pass the same idempotency_key on a retry without post_id so a network error never makes two posts; with post_id a retry is safe as is: a post already publishing or published answers its current statuses and is never published twice. Returns success, post_id and results[] with one row per account (platform, username, status, error). Call get_post afterwards to show exactly what was scheduled. Does NOT publish now unless publish_now is true.

Shows an upload card where the user picks images or videos from their device (images up to 20 MB, videos up to 1 GB); the card stores the original files in the workspace. Use this in a chat app that shows cards (Claude.ai, Claude Desktop, Claude mobile) whenever the user attached a file in the chat or wants to add one from their device: you cannot read their attachment, so let them pick it here. When they finish, the card adds each file name and media_key to your context and asks the user to send a message; pass those media_key values to create_post or update_post. Returns nothing to attach by itself. Does NOT work in Claude Code or a terminal (use create_upload_url there) and does NOT take a link (use upload_media).

Stores the original image or video in the workspace from a file the chat app hands over, a public URL (up to 1 GB for a video) or inline base64 (up to 3 MB), checking the real file type and the storage quota. Use this when the user gives you a link to attach to a post, or when the chat app hands you their attachment as `file` (ChatGPT does); then pass the returned media_key to create_post or update_post. `file` is filled by the chat app with an https download link, never by you: a path you see such as /mnt/user-data/uploads/… is on the user's side and cannot be read here. For a file the user attached or has on their device, call upload_file in a chat app that shows cards (Claude), or create_upload_url in Claude Code or a terminal. Use `base64` only with the original bytes of a small image you read from disk; never draw, reconstruct, re-encode or compress an image you have only seen. Returns media_key, bytes, content_type and source. Does NOT attach the file to any post by itself and does NOT accept private or local-network URLs.

Reserves storage for one file and returns a presigned upload_url (valid 1 day) plus the media_key it will be stored under. Images up to 20 MB, videos up to 1 GB. Use this in Claude Code, a terminal or a script, for a local file or any video: PUT the ORIGINAL file bytes, unmodified, to upload_url with the returned content-type header and exactly `bytes` bytes, then pass media_key to create_post or update_post. Never re-encode, resize or compress the file first. In a chat app that shows cards (Claude.ai, Claude Desktop, Claude mobile) call upload_file instead: the user picks the file and nothing has to be allowed. The PUT goes to the storage host in upload_url (<account>.r2.cloudflarestorage.com). A code sandbox that blocks it needs that host allowed: On Claude.ai a Pro or Max user allows it in Settings → Capabilities; on a Team or Enterprise plan the organization owner adds it in Admin settings → Capabilities → Additional allowed domains. Returns upload_url, media_key, headers and expires_in. Does NOT upload anything by itself, and does NOT accept a URL or base64; use upload_media for those.

Called only by the JuzPost upload card, never by the model. Reserves storage for one file and starts a multipart upload. Returns media_key, upload_id, part_size and parts.

Called only by the JuzPost upload card, never by the model. Stores one part of a file started with upload_begin: the original bytes as base64, exactly part_size bytes except the last part. Returns part_number and bytes.

Called only by the JuzPost upload card, never by the model. Completes an upload once every part is stored. Returns media_key, bytes and content_type.

概览

What it is

Draft, schedule and publish social media posts from Claude, ChatGPT, Cursor or any MCP client. Write a post once, attach images or video, pick accounts and schedule or publish to 11 networks: X, LinkedIn, Instagram, Facebook, TikTok, YouTube, Threads, Bluesky, Pinterest, Tumblr and WordPress. Tools check each platform's caption, media and format limits before posting, list the queue, and edit, reschedule or delete posts. Tools: get_context, list_workspaces, switch_workspace, list_accounts, list_groups, list_options, get_platform_limits, create_upload_url, upload_media, upload_file, create_post, schedule_post, update_post, get_post, list_posts, delete_post. Pricing: the MCP server, REST API and CLI are on paid plans from Solo ($19/mo, 7-day trial). A free scheduler plan (2 accounts, 15 queued posts, no X) exists in the web app but does not include MCP access.

From the publisher's website: Manage, schedule, and grow your social media with JuzPost. Social media scheduling software to plan, publish, and track your content from one dashboard.

Connect

  • Endpoint: https://www.juzpost.com/mcp (Streamable HTTP)
  • Authentication: no authentication

Claude Code:

claude mcp add juzpost --transport http https://www.juzpost.com/mcp

Other clients (mcpServers config):

{ "mcpServers": { "juzpost": { "type": "http", "url": "https://www.juzpost.com/mcp" } } }

Tools

Read from the server's tools/list on 2026-11-08:

  • get_context — Reports who this connection is, the one workspace it acts on (use switch_workspace to change it), the plan, billing state, entitlements, quotas, limits and a plain-language list of what is blocked right now
  • list_workspaces — Lists every workspace the user belongs to, marks the one this connection acts on, and says what each allows through the connector: none (Free or no plan) or full (Solo, Growth, Pro)
  • switch_workspace — A connection acts on one workspace at a time
  • list_accounts — Lists the social accounts connected to the workspace, with health, how many posts are queued on each, and the effective limits for that account
  • list_options — Lists the choices one account offers for a setting the schedule needs, read live from the platform
  • get_platform_limits — Returns the full publishing rules for one platform or all of them: caption and title limits and units, media counts, sizes, formats, whether media is required, hashtags, mentions, native scheduling, plus the global file rules
  • list_groups — Lists channel groups (named sets of accounts) with their member account ids
  • list_posts — Lists posts in the workspace: drafts, scheduled, published and failed
  • get_post — Fetches one post with its per-account rows: status, publish time, published time and any error per account
  • create_post — Creates a draft post with everything the composer saves: caption, title, description, hashtags, media, the accounts it goes to, per-account text (account_overrides, channel_overrides), per-account media and covers, and each platform's settings
  • update_post — Edits a draft or a scheduled post, the same edit the composer makes: caption, title, description, hashtags, type, media keys, cover, accounts, per-account text, media and covers, platform settings, and the time
  • delete_post — Permanently deletes a post in any status (draft, scheduled, failed or published) from JuzPost, with its per-account rows
  • schedule_post — Schedules a post to one or more accounts at publish_at, or publishes immediately with publish_now=true
  • upload_file — Shows an upload card where the user picks images or videos from their device (images up to 20 MB, videos up to 1 GB); the card stores the original files in the workspace
  • upload_media — Stores the original image or video in the workspace from a file the chat app hands over, a public URL (up to 1 GB for a video) or inline base64 (up to 3 MB), checking the real file type and the storage quota
  • create_upload_url — Reserves storage for one file and returns a presigned upload_url (valid 1 day) plus the media_key it will be stored under
  • upload_begin — Called only by the JuzPost upload card, never by the model
  • upload_part — Called only by the JuzPost upload card, never by the model
  • upload_finish — Called only by the JuzPost upload card, never by the model

Notes

  • Description above is the publisher's own summary from their submission; check the website for plans, pricing and limits.
  • The endpoint answered a standard MCP initialize request when checked on 2026-11-08.

Sources: Website, Submission.

常见问题

1

JuzPost 远程 MCP 服务器是什么?

JuzPost 的远程 MCP 服务器是一个托管的 Model Context Protocol 端点,地址是 https://www.juzpost.com/mcp,AI 助手无需在本地安装或运行任何东西即可连接。

2

怎么连接 JuzPost 的 MCP 服务器?

把端点 https://www.juzpost.com/mcp 添加到任意支持 MCP 的客户端,比如 Claude Code、Cursor 或 VS Code。本页的接入代码块可以一步配置好每个客户端。

3

JuzPost 的 MCP 服务器需要认证吗?

不需要。JuzPost 的 MCP 服务器不需要认证——直接用端点地址连接即可。

4

JuzPost 的 MCP 服务器用的是哪种传输方式?

JuzPost 暴露的是 streamable-http 端点,这是远程 MCP 服务器普遍使用、主流客户端都支持的传输方式。

评论