Skip to main content
Glama
Perufitlife

PostWire

by Perufitlife
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

postwire-mcp

Your agent writes the post, picks the right shape for each network, and publishes it.

An MCP server for PostWire. Give Claude, Cursor, or any agent one idea and it publishes a native post to TikTok, Instagram, YouTube, X, LinkedIn, Reddit, Bluesky, Mastodon, Telegram and Discord — not the same text pasted ten times.

you:    "post the demo video — we shipped scheduling today"
agent:  → YouTube  title + description + tags, 16:9
        → TikTok   hook in the first line, 4 tags
        → LinkedIn no link in the body, link in the first comment
        → X        under 280, link in a reply
        published. 4/4.

Quick start

  1. Get a free API key at postwire.io/dashboard.html and connect an account. One OAuth click — PostWire already holds the platform approvals, so there is no app review to wait for.

  2. Add it to your MCP client:

{
  "mcpServers": {
    "postwire": {
      "command": "npx",
      "args": ["-y", "postwire-mcp"],
      "env": { "POSTWIRE_API_KEY": "pw_live_your_key" }
    }
  }
}

Client-specific setup: Claude Desktop · Claude Code · Cursor · VS Code · Windsurf

No key yet? list_platforms still answers, so you can see what is supported before signing up.

Related MCP server: Publora MVP MCP Server

Tools

Tool

What it does

generate_posts

Smart Distribute. One prompt → a draft written for each platform: character limits, hashtag conventions, YouTube SEO title+tags, hook-first captions for TikTok, link-in-comment for LinkedIn. Returns drafts for you to review.

post_to_social

Publishes. Takes one text for all, or per_platform drafts from generate_posts.

get_post_status

Publish state for platforms that report one back (TikTok and YouTube process asynchronously).

list_platforms

Every supported network and the fields it needs. Works without a key.

my_account

Plan, posts used this month, which accounts are connected.

Failures are refused up front rather than half-published: a video network with no video, text over a platform's limit, or an account that was never connected all come back as a clear error before anything goes out. A four-network post never leaves you with two live and two silently missing.

Platforms

One OAuth click — TikTok · Instagram · YouTube · X · LinkedIn · Reddit · Facebook Token or webhook — Bluesky · Mastodon · Telegram · Discord

Pricing

Per brand, never per network. Connect a business once and every one of its accounts is included.

Brands

Posts/month

Free

1

30

no card

Starter

3

300

$9/mo

Pro

10

2,000

$29/mo

Agency

50

15,000

$99/mo

Ten client businesses on five networks each is $29 here. Buffer bills per channel; Ayrshare's comparable tier is $299.

REST too

Everything the MCP server does is a plain HTTP call, if you would rather not run an MCP client:

curl -X POST https://postwire.io/api/post \
  -H "Authorization: Bearer $POSTWIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platforms":["x","bluesky"],"text":"shipped."}'

Docs: postwire.io

MIT © PostWire

Available Tools

2 tools
list_platformsA

List the social platforms PostWire supports and the fields each needs.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description clearly indicates it's a read-only listing operation that returns platforms and their required fields, with no side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single concise sentence front-loading the action 'List the social platforms', with no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple with zero parameters and no output schema; description fully covers what the tool does and what it returns, making it complete for decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist; description compensates by explaining output content (platforms and fields), which is sufficient for the tool's purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'List' and the resource 'social platforms', and mentions 'fields each needs', providing a specific purpose that distinguishes it from the sibling 'post_to_social'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage context (use before posting to discover required fields) but no explicit when/when-not or alternatives; adequate given the tool's simplicity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

post_to_socialA

Publish a post (optionally with a photo or video) to one or more social platforms via PostWire. Connect accounts first at https://postwire.io/dashboard.html. Returns per-platform results.

ParametersJSON Schema
NameRequiredDescriptionDefault
platformsYese.g. ['x','tiktok','bluesky']
textYespost text / caption
video_urlNooptional public URL of a video
photo_urlNooptional public URL of a photo

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. It discloses that it returns per-platform results, and mentions optional photo/video. It does not contradict any annotations (none exist). It does not detail side effects or permissions, but for a post tool the behavior is fairly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no wasted words. First sentence defines the action and optional media, second gives the prerequisite and return value. Efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main action, optional media, prerequisite, and return structure. However, it lacks details on error handling, platform validation, or what happens if a platform is not connected. Given no output schema and no annotations, a bit more context would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds that photo/video are optional and that it uses PostWire, but does not provide additional detail on parameter formats or constraints beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Publish), resource (post), and scope (to one or more social platforms via PostWire). It distinguishes from the sibling tool list_platforms, which is for listing available platforms, not posting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly mentions a prerequisite: connecting accounts at the provided URL. It implies usage for publishing posts, and the sibling tool list_platforms complements it. However, no explicit when-not-to-use or alternative scenarios are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedlist_platforms
    • First observedpost_to_social
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0
Disambiguation5/5

The two tools have completely distinct purposes: one lists supported platforms and their fields, the other posts content. There is no ambiguity or overlap.

Naming Consistency5/5

Both tools use a consistent verb_noun pattern: list_platforms and post_to_social, making the naming predictable and clear.

Tool Count4/5

With only 2 tools, the server is minimal but well-scoped for its focused domain of posting social media content via PostWire. The count is slightly thin but reasonable.

Completeness4/5

The tools cover the core functionality of listing supported platforms and posting content. Missing features like post history or schedule management are minor gaps for this server's stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • @posteverywhere/mcp by posteverywhere

    @posteverywhere/mcpofficial

    posteverywhere
    A
    license
    A
    quality
    A
    maintenance
    Enables AI assistants to schedule and publish social media posts to platforms like Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, and Pinterest using natural language.
    33
    163
    3
    MIT

  • socialclaw

    ndesv21
    A
    license
    Not graded
    quality
    A
    maintenance
    Social media scheduling and publishing for AI agents. 17 validation-first tools to post to X, LinkedIn, Instagram, TikTok, YouTube, Reddit, Discord, Telegram, and more through one connected workspace.
    316
    86
    MIT

  • kadenzo-mcp

    Kadenzo
    A
    license
    A
    quality
    B
    maintenance
    Schedule, manage, generate, and analyze social posts across 11 networks (Instagram, TikTok, X, LinkedIn, YouTube, Facebook, Pinterest, Threads, Bluesky, Mastodon, Telegram) from any AI agent — 13 tools covering scheduling, media upload, AI caption generation, best-times, analytics, listening, and comments.
    13
    119
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Perufitlife/postwire-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server