Postmcp MCP server

Read from the package source without running it. The installed server may list more.

• create_postwrite action

  Schedule or immediately publish a post to specific connected social profiles. Prefer targetAccounts so the post lands only on the profiles you name. Every targeted profile becomes its own post with its own id, so each can be edited, retried or cancelled on its own - the response lists them all. With publishImmediately, each delivered profile comes back with a `url` to the live copy; pass those on

• delete_postwrite action

  Cancel and delete a scheduled or failed post from the database.

• generate_image

  Generate an image for a post from a text prompt and return its hosted URL, ready to pass to create_post as mediaUrl. Pass a brandingId from list_brandings to match the workspace's visual style. Spends AI tokens.

• get_account_health

  Report connections whose access token has expired or is about to, and which therefore need the user to reconnect. Check this before scheduling anything far out - a post scheduled onto a dead connection fails silently at publish time.

• get_connected_accounts

  List every connected social profile in the workspace with the profileId needed to target it. Call this before creating a post so the post reaches the intended profile rather than every account on a platform.

• get_postwrite action

  Fetch a single post by id, including per-profile delivery status, the live URL of each published copy, and the error for any profile that failed.

• get_user_info

  Retrieve details of the logged-in user including subscription plan, credit balance, AI token count, the active workspace, and the caller's role in it.

• list_brandings

  List the workspace's brand kits: tone of voice, audience, keywords, and reference style images. Use one to keep drafted copy on-brand, and pass its id to generate_image for on-brand visuals.

• list_posts

  Retrieve scheduled, published, draft, and failed posts, newest first, with per-profile delivery status. Every profile that received a post carries `url`, the link to the live copy - give the user that link when they ask where a post went. Returns pagination plus counts per status.

• list_workspaces

  List every workspace (project) the user belongs to, with the id to pass as workspaceId, the caller's role, and which one is the default. Call this first whenever the user mentions a client, brand, or workspace by name.

• multicallwrite action

  Run several PostMCP tools in one request, in the order given. Use it whenever a task needs more than one call - scheduling a week of posts, checking accounts then publishing, or cancelling a handful of posts - instead of one round trip per call. Calls run sequentially and every tool name is validated before anything executes, so a typo cannot leave half a batch written. Cannot nest: a call inside

• preflight_postwrite action

  Dry-run a post before creating it: checks copy against each platform's character limit, flags profiles that are not connected or need reconnecting, warns when a platform requires media, reports each target's video limit when a video is attached, and reports the credit cost against the workspace balance. Costs nothing and publishes nothing. Run this before create_post whenever the copy is long, car

• publish_post_nowwrite action

  Broadcast an existing scheduled post immediately to its platforms. Also the way to retry a failed post: profiles that already received it are skipped, so only the stragglers go out. The returned post carries a `url` per delivered profile - report those links rather than only saying it published.

• reschedule_postwrite action

  Move a post to a different date and time, keeping its copy and target profiles. A failed or draft post is re-armed by this and will go out at the new slot; profiles that already received it are not sent to again. Published posts and posts currently publishing cannot be moved.

• reset_stuck_postwrite action

  Release a post left stuck mid-publish so it can be retried. Profiles that already went out keep their delivered state, so retrying afterwards will not double-post. Only use this on a post whose status is 'processing'; if it started publishing recently the call is refused unless force is true.

• update_postwrite action

  Update the fields (content, target profiles, schedule date/time) of an existing post. To move a post to a different slot without touching anything else, use reschedule_post.

• Code scan16 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 16 days ago15/15
• Maintainer identityregistry namespace matches repository owner6/10

Safety score

80/100

higher than 69% of 874 Sales and outbound servers

Tools

16

the typical Sales and outbound server has 8

Tools that change things

56%

typical: 11%. Fewer write tools means less an agent can break

Downloads a week

23

more than 12% of 157 Sales and outbound servers with a package

Postmcp: common questions

Is Postmcp MCP server safe?

Mostly: it is graded B (80/100). Read the Postmcp safety report

How do I install Postmcp?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Postmcp need an API key?

Yes. The registry entry asks for POSTMCPAI_API_KEY.

Is Postmcp maintained?

The last commit was 35 days ago (2026-10-01). The latest release is v1.0.1.

What can I use instead of Postmcp?

Servers from other publishers that do the same job: Postbase MCP server, Chirpie MCP server and Upload-Post MCP server. Compare all Postmcp alternatives.

How does Postmcp compare with other Sales and outbound MCP servers?

safety score 80/100 (higher than 69% of 874 Sales and outbound servers); tools 16 (the typical Sales and outbound server has 8); tools that change things 56% (typical: 11%. Fewer write tools means less an agent can break). Full comparison.