Skip to content
PostyDashboardFinish setupGet started

OpenCode MCP serverfor social media scheduling

Add Posty as an OpenCode MCP server and move from a commit message to a scheduled post in the same session. Sign in with Posty. Your workspace permissions apply.

Connect OpenCodeCreate your workspace
Remote MCP server URL
https://api.posty.social/mcp
Transport
Streamable HTTP
Sign in
OAuth with your Posty account
Permissions
Your workspace role, checked per call
Plans
Growth and Accelerate
Stored in
opencode.json

Connect OpenCode in three steps

Posty is a remote MCP server. OpenCode adds it by URL, you sign in once in the browser, and every tool call after that runs with your own workspace permissions.

Official OpenCode MCP documentation
  1. 1

    Add the server

    Run the guided add command. Name the server posty, choose Remote and enter https://api.posty.social/mcp as the URL. OpenCode writes a remote entry with OAuth detection to your configuration.

    OpenCode setup
    opencode mcp add
  2. 2

    Sign in and approve access

    Posty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere. OpenCode also starts the sign-in on its own the first time a tool answers that it needs one.

    Authentication command
    opencode mcp auth posty
  3. 3

    Choose a workspace and start

    Check the connection with the list command, then ask OpenCode to list your Posty workspaces and name the one you want in each request.

    Check the connection
    opencode mcp list

What OpenCode can do once it’s connected

Every tool mirrors one operation of the public API, so anything a script can do, your assistant can do, within your role. The server publishes its full tool catalog with every schema.

Posts and scheduling
Create drafts with text and settings per channel, move them onto the calendar, reschedule up to 50 at once and read delivery history.create_postupdate_post_contentbulk_schedule_posts
Approvals
Submit a post for review, approve it or request changes, and see who has been asked and how each ask ended. Approval rules stay in force.act_on_postlist_post_review_requestsget_post_history
Media
Upload images and video into the library, organise folders, set alt text and attach files to a post’s channels.create_media_uploadreplace_post_content_mediaset_media_alt_text
Campaigns
Create a campaign brief with objective, personas and dates, file posts under it and read its results against the brief.create_campaignadd_post_to_campaignget_campaign_results
Analytics
Workspace KPIs against the previous period, per post performance, audience demographics and the metrics each platform reports.get_analytics_overviewget_analytics_detailget_post_native_metrics
Inbox
Read comments and direct messages from connected channels, reply, assign a teammate and change a conversation’s status.list_inbox_conversationslist_post_commentscreate_post_comment

Things to ask OpenCode

Replace “Launch” with your workspace name. Each one maps onto the tools above, and OpenCode shows you the calls before they run.

  • From commits to a post

    Example prompt
    Read the commits since the last tag and draft a short LinkedIn post about what changed in my Launch workspace. Keep it as a draft.

  • Schedule the backlog

    Example prompt
    List the unscheduled drafts in Launch and spread them over weekday mornings next week at 9am local time.

  • Weekly report

    Example prompt
    Give me a short summary of how Launch performed over the last seven days compared with the week before.

Your workflow.
Still your call.

Posty checks workspace membership and permissions on every call. Drafts, approvals and scheduling follow the same rules as the app, and a token never freezes a permission you have since lost.

You can work across any workspace you have access to. Tell your assistant which one to use, review its drafts, and publish when you’re ready. See the roles and visibility matrix for what each role can do.

Questions about Posty and OpenCode

Can I put the server in opencode.json for my team?
Yes. A remote server is an entry under mcp in opencode.json with its type set to remote and the Posty server URL; an empty oauth object turns on sign-in detection. Commit that file and each teammate signs in with the auth command on their own machine.
Where does OpenCode keep the sign-in?
In its own credential store in your home directory, separate from the configuration file, so a committed opencode.json never contains a token. The logout command removes the stored credential for a server.
What if the tools do not appear?
Run the OpenCode MCP debug command with the server name. It tests the connection and the sign-in discovery step and reports what failed. The auth list command shows which servers are signed in.
Which permissions does the assistant get?
Exactly yours. Every tool call checks your workspace membership and role at that moment, so an assistant can only see the workspaces you belong to and do what you could do in the app. Approval rules still apply: a workspace that requires review before scheduling requires it from your assistant too.
Which Posty plans include MCP access?
The Growth and Accelerate plans, the same plans that include the public API. A workspace on another plan returns a clear plan error instead of connecting.
Can one connection work across several workspaces?
Yes. Ask the assistant to list your workspaces first, then name the one you mean in each request. Every tool takes a workspace, so an agency can draft for one client and check analytics for another in the same conversation.

Use Posty from another assistant too

One server, the same sign-in and the same permissions in every client. Each one has its own guide.

Your assistant. Your workspace. Your rules.

Create a workspace, connect OpenCode and keep every post inside the approvals and permissions your team already uses.

MCP access is included on Growth and Accelerate, from $39 per workspace a month. Compare plans

Create your workspace