OpenCode social media posting: connect PostWire's MCP server

Set it up and post, step by step

1. Add the server to opencode.json

   Put this in opencode.json in your project root, or in ~/.config/opencode/opencode.json to have it in every project. It is OpenCode's own form for a remote MCP server; no headers and no oauth block are needed, because OpenCode detects that PostWire asks for a sign-in and registers itself.

   {
     "$schema": "https://opencode.ai/config.json",
     "mcp": {
       "postwire": {
         "type": "remote",
         "url": "https://postwire.io/api/mcp",
         "enabled": true
       }
     }
   }

2. Sign in with your email

   Run opencode mcp auth postwire. OpenCode opens your browser on PostWire's sign-in; type your email and the 6-digit code PostWire sends you, and approve. That also creates a free PostWire account if you have none: no password and no card. OpenCode stores the token and refreshes it; opencode mcp list shows the server and its auth status.

3. Check that the tools are there

   Start OpenCode and ask "what PostWire tools do you have?". It lists 26, among them postwire_generate_posts, postwire_post_to_social, postwire_schedule_post, postwire_list_scheduled_posts and postwire_get_post_status. If none show up, opencode mcp debug postwire shows the connection and the sign-in state.

4. Connect your social accounts

   Ask "connect my LinkedIn and my Bluesky". create_connect_link returns a one-hour link; open it and sign in to each network on its own page (Bluesky, Mastodon, Telegram and Discord take an app password, a token or a webhook there). OpenCode never sees those passwords: it holds a PostWire token, and PostWire holds the accounts.

5. Let PostWire write each network's post

   "Read CHANGELOG.md and write this release's posts for LinkedIn, Bluesky and Mastodon." generate_posts returns one draft per network and publishes nothing: a first-person post for LinkedIn, a conversational one of up to 300 characters for Bluesky, a community-first toot with CamelCase hashtags for Mastodon.

6. Publish, or schedule it

   After you approve, OpenCode calls post_to_social, or schedule_post with a run_at time (or "next_slot" for your next free queue slot):

   {
     "name": "schedule_post",
     "arguments": {
       "platforms": ["linkedin", "bluesky"],
       "per_platform": {
         "linkedin": { "text": "We shipped CSV import this week. Here is what took us three tries to get right…" },
         "bluesky": { "text": "csv import is live. it took us three tries, ask me which one hurt most" }
       },
       "run_at": "2026-11-03T09:00:00-05:00"
     }
   }

7. Ask what is queued and what went out

   "What's scheduled this week?" calls list_scheduled_posts; cancel_scheduled_post removes one before it goes out, and get_post_status returns each network's result with the link to the live post.

The config and commands are OpenCode's own, from its MCP servers documentation (read Oct 29, 2026); if your version differs, that page is the reference. Prefer to set it up by hand first? Open the dashboard, connect your accounts under Accounts and copy your key under API & MCP.