posterly
Back to Blog
AI Agents

Social Media MCP Server for Smithery: Setup Guide

Connect Smithery to posterly's social media MCP server, authorize your account safely, and schedule posts from an MCP-compatible AI agent.

By ··9 min read
Social Media MCP Server for Smithery: Setup Guide

If you want an AI agent to do more than write a caption, it needs a safe way to reach the tools that can actually schedule, publish, and measure social content. That is what a social media MCP server provides.

Smithery makes MCP servers easier to discover and connect. posterly's Smithery listing gives an MCP-compatible agent a managed connection to posterly's hosted toolset, while posterly handles the social accounts, scheduling rules, media, analytics, and publishing.

The important distinction is simple:

ServiceWhat it does
SmitheryHelps you find and connect an MCP server to an agent
posterlyConnects to your social accounts and provides the scheduling, publishing, media, and analytics tools
Your AI agentUnderstands your request, chooses the appropriate tool, and asks for confirmation before consequential actions

Smithery does not receive shared access to every posterly customer, and connecting posterly does not make your account public. Each user signs in and authorizes their own posterly account.

Quick answer: can Smithery schedule social media posts?

Yes, through a social media MCP server such as posterly.

After you connect your own posterly account, an MCP-compatible agent can use posterly's 72 hosted tools to list connected accounts, inspect scheduled posts, validate content, upload media, find available time slots, schedule posts, and read supported analytics.

posterly supports 18 publishing destinations:

  • Instagram
  • Facebook
  • TikTok
  • X
  • LinkedIn
  • YouTube
  • Pinterest
  • Threads
  • Google Business Profile
  • Telegram
  • Bluesky
  • Discord
  • Slack
  • Mastodon
  • Dev.to
  • Hashnode
  • WordPress
  • Lemmy

The available settings and analytics vary by platform. Your agent can call list_platforms and get_platform_schema instead of guessing which fields a network supports.

What you need before connecting

You need:

  1. A Smithery account.
  2. A posterly account with an active plan.
  3. The posterly API and MCP add-on.
  4. An MCP-compatible client or agent supported by your Smithery workflow.
  5. At least one social account connected to posterly if you want to schedule immediately.

Individual posterly plans start at $7 per month, and API/MCP access is a $3-per-month add-on. Agency API/MCP pricing is different. If the add-on is not active when you authorize Smithery, posterly will prompt you to subscribe before the connection can use paid tools.

This is not free access to posterly's API. Every Smithery user brings their own posterly account and subscription.

How to connect posterly to Smithery

1. Open the posterly server on Smithery

Go to the posterly MCP server listing on Smithery.

The listing describes the server, its tools, uptime, and available connection options. Smithery's interface may label the next action Connect, Add, or Try now, depending on where you are using it.

2. Add posterly to your Smithery toolbox

Choose the connection option for your agent or toolbox. Smithery will start an OAuth authorization flow rather than asking you to paste a posterly API key into the listing.

OAuth is useful here because it creates a revocable, account-specific connection. You do not need to expose your posterly password or copy a long-lived API key into a third-party form.

3. Sign in to your own posterly account

Your browser will open a page on poster.ly.

Check two things before continuing:

  • The address bar is on the poster.ly domain.
  • The email shown is the posterly account you intend to connect.

If you are not signed in, sign in or create a posterly account. New users may also need to select a plan and activate API/MCP access before authorization completes.

4. Review the requested permissions

The authorization page explains what the connection can do. The Smithery connection currently requests these posterly permissions:

  • Accounts read: see which social accounts you connected.
  • Accounts write: disconnect a social account from posterly.
  • Posts read: list your scheduled and published posts.
  • Posts write: schedule, edit, and delete posts on your behalf.
  • Media write: upload images and videos to your media library.
  • Analytics read: read supported engagement and follower analytics.

These are meaningful permissions. Only approve them when you want the connected agent to perform those actions.

posterly also marks its MCP tools with safety information so compatible clients can distinguish read-only calls from actions that change data. Destructive and publishing workflows require explicit confirmation where the tool contract calls for it.

5. Select Allow

After you approve access, posterly returns you to Smithery. Smithery stores the resulting connection for your account and handles the OAuth session and token refresh needed to keep it working.

The token represents your posterly account. Another Smithery user must complete the same authorization flow for their own posterly account; they do not inherit your connection, social accounts, posts, or analytics.

6. Test with a read-only request

Start with something that cannot publish or delete anything:

  • "Which social accounts do I have connected in posterly?"
  • "Show my scheduled posts for next week."
  • "What workspaces can this connection access?"
  • "How did my LinkedIn account perform over the last 14 days?"

This confirms the connection and gives you a chance to check that the correct posterly workspace is active.

7. Validate before scheduling

For a first publishing test, ask the agent to prepare and validate a post without creating it:

Draft a LinkedIn post about our product launch for tomorrow at 10am. Validate the complete post, show me the final preview, and do not schedule it until I confirm.

The validate_post tool checks the account, caption, schedule, media, and platform settings without creating a post or enqueueing publication. Once the preview is correct, confirm the exact action and let the agent call create_post.

That validate-then-confirm pattern is the safest way to use any social media MCP server.

Useful prompts for a social media MCP agent

Once connected, try workflows like:

Plan and schedule

  • "Find the next three open posting slots for my LinkedIn account."
  • "Show me everything scheduled this week before we add another post."
  • "Turn this announcement into separate drafts for LinkedIn, Instagram, and X."
  • "Validate the three drafts and show me their platform-specific settings."
  • "Schedule the approved versions after I confirm each account and time."

Work with media

  • "Upload this image and prepare an Instagram post, but do not schedule it yet."
  • "Use this public video URL to create a TikTok draft."
  • "Check whether this media meets the selected platform limits."

Hosted MCP calls use JSON, so a managed Smithery connection works best with public media URLs or clients that support the required upload step. The local posterly MCP package is a better option when an agent needs to read large files directly from your computer.

Review performance

  • "Compare my recent LinkedIn posts by engagement."
  • "Summarize follower growth for the last 30 days."
  • "Which recent posts performed above their normal baseline?"
  • "Draft three follow-up ideas based on what has worked."

Analytics availability depends on what each social network exposes and which posterly plan features are active.

Is connecting Smithery to posterly safe?

The connection is designed around three boundaries:

  1. You authorize your own account. Smithery users do not share one posterly credential.
  2. Sensitive steps stay in your browser. Login, payment, and social-network authorization happen on posterly or the relevant provider's domain.
  3. Access can be revoked. You can remove the connection instead of rotating a password shared across services.

The authorization screen should still be treated seriously. posts:write, media:write, and accounts:write allow real changes. Review the requested scopes, use an agent you trust, and ask the agent to preview consequential actions before confirming them.

If you only want to inspect an account, say that explicitly. A well-behaved agent should use read-only tools for a read-only request.

Troubleshooting a Smithery connection

"Connection failed" after authorization

Try these checks in order:

  1. Return to the posterly listing and retry the connection.
  2. Confirm you are signed in to the intended posterly account.
  3. Check that the posterly subscription and API/MCP add-on are active.
  4. Make sure you selected Allow, rather than closing or denying the authorization page.
  5. Remove the incomplete Smithery connection and create a fresh one if the previous session expired.
  6. Test with a read-only request such as whoami or list_accounts.

If the problem continues, record where the flow stopped and contact posterly support. Never send support your password, OAuth token, or full API key.

The agent can connect but cannot schedule

Check:

  • A social account is connected in posterly.
  • The connection has posts:write.
  • The selected posterly workspace can access the chosen social account.
  • The requested platform supports the media and post type.
  • The scheduled time includes the intended timezone.
  • The agent validated the final payload before creating it.

posterly returns actionable errors for missing settings, unsupported media, expired connections, insufficient subscription access, and rate limits. Ask the agent to explain that message in plain language rather than repeatedly retrying the same call.

The wrong posterly account was authorized

Disconnect posterly from Smithery, sign out of the unwanted posterly session, and reconnect. Confirm the email shown on the posterly authorization page before selecting Allow.

Smithery social media MCP FAQ

Is Smithery a social media scheduler?

No. Smithery is an MCP discovery and connection platform. The posterly MCP server supplies the social media scheduling, publishing, media, and analytics capabilities.

Can Smithery post to Instagram, LinkedIn, or TikTok?

Yes, when Smithery is connected to posterly and your corresponding social account is connected in posterly. Platform permissions, media requirements, and post settings still apply.

Does connecting posterly give every Smithery user access to my account?

No. Your OAuth connection belongs to your Smithery and posterly account. Every other user must sign in and authorize their own posterly account.

Is the posterly MCP server free through Smithery?

No. Smithery does not bypass posterly billing. API and MCP access requires an active posterly plan plus the appropriate API/MCP add-on.

Do I need to paste an API key into Smithery?

The managed hosted connection uses posterly OAuth, so the normal Smithery flow does not require you to paste a posterly API key. The local npm/stdio connection is a separate option that uses a dashboard-created API key.

Can the agent publish without asking me?

The connection has the technical ability to call write tools when the authorized scope allows it. posterly's consequential MCP actions use confirmation safeguards, but you should also tell the agent to validate and preview content before publishing. Only connect agents you trust.

Can I revoke access later?

Yes. Remove or disconnect the posterly connection from your Smithery connections. You can then authorize it again later if needed.

Connect your agent

Open posterly on Smithery to create a managed connection, or read the complete posterly MCP setup guide to compare hosted OAuth with the local npm package.

If you do not have a posterly account yet, create one here. Your account remains yours: Smithery provides the connection, while posterly provides the social publishing system behind it.

AI AgentsMCPSmitherySocial Media SchedulingOAuthAutomation

Related Articles