10 DAYS ONLY · $500 VALUE Top 100 Viral Hooks + Repurpose Engine (Claude Skills) Start free → Start free →
OpenCode

OpenCode Social Media MCP Setup

OpenCode connects to a social media MCP server with a URL and headers, and it supports automatic OAuth through dynamic client registration. Blotato serves dynamic client registration, so OpenCode can complete the OAuth handshake without you pre-registering an application.

Endpoint https://mcp.blotato.com/mcp OAuth or header

Updated August 2026

How to connect OpenCode to social media

  1. Connect your social accounts in Blotato.
  2. Add a remote MCP server in your OpenCode configuration pointing at https://mcp.blotato.com/mcp.
  3. Either let OpenCode negotiate OAuth automatically, or set blotato-api-key as a header.
  4. Restart OpenCode so the tools load.
Remote server entry in opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "blotato": {
      "type": "remote",
      "url": "https://mcp.blotato.com/mcp",
      "enabled": true,
      "headers": {
        "blotato-api-key": "YOUR_API_KEY"
      }
    }
  }
}
OpenCode MCP documentation showing remote server configuration
OpenCode's own MCP documentation, showing where the remote server config goes.

How do I know it worked?

Ask OpenCode to list your connected accounts. It calls blotato_list_accounts and returns your platforms, which confirms both the connection and the authentication in one step. If you see your accounts, setup is done.

First prompt to run
What social media accounts do I have connected?
An AI agent answering "what social accounts do i have connected?" by calling Blotato and listing 10 connected social media accounts across Twitter, Bluesky, Instagram, Threads, LinkedIn, Facebook, YouTube, Pinterest, and TikTok
The reply you are looking for: the agent calls Blotato and lists every connected account. Here it returns 10 accounts across all nine platforms.

Worth knowing before you rely on it: analytics prompts only return data for X, Instagram, Facebook, Threads, and Bluesky. The other four platforms publish normally but report no metrics yet.

What to ask OpenCode once it is connected

Draft the captions on the cheap model, then publish.
OpenCode configures a model per agent and lets you switch agents mid-session, so drafting can run somewhere inexpensive while blotato_create_post fires from whichever agent holds the tools. The publish call costs the same either way.
Keep these tools away from my coding agents.
Scope the server to one agent rather than globally. A publishing agent holds the Blotato tools and the coding agents never see them, which also keeps 28 tool definitions out of their context window.
Turn this YouTube video into posts.
blotato_create_source extracts the content and blotato_get_source_status polls until it resolves, then the text feeds blotato_create_post.

What breaks, and how to fix it

OpenCode is model agnostic, and that is where the friction usually is. The connection can be perfect while the model you selected handles tool calling poorly, which looks like a broken server but is a model choice. If the tools are listed and simply are not called, change the model before re-checking the config. Note also that MCP tools enter the context window, so a server with a large surface competes with your actual prompt for room.

What is different about OpenCode

OpenCode is the only client here that can negotiate OAuth automatically through dynamic client registration, so it completes an OAuth setup with no application registered in advance and no key pasted anywhere. It also scopes servers two ways, globally or per agent, so a publishing agent can hold the Blotato tools while your coding agents never see them, and pairing that with its model-per-task switching lets you draft captions on one model and run the publish call on another.

Vendor documentation: OpenCode MCP setup. For how a client discovers and calls tools once connected, see the MCP client concepts reference.

FAQ

OpenCode social media FAQs

01 Can OpenCode post to social media?
Yes. OpenCode cannot reach a social account on its own, because it has no platform credentials. Connecting it to Blotato's hosted MCP server at https://mcp.blotato.com/mcp gives it tools to publish and schedule across nine platforms: X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest. OpenCode authenticates with oauth or header.
02 How do I connect OpenCode to social media?
OpenCode connects to a social media MCP server with a URL and headers, and it supports automatic OAuth through dynamic client registration. Blotato serves dynamic client registration, so OpenCode can complete the OAuth handshake without you pre-registering an application.
03 How do I set up OpenCode for social media?
Setting up OpenCode for social media takes one connection. Connect your social accounts in Blotato, then give OpenCode the hosted MCP endpoint https://mcp.blotato.com/mcp and authenticate with oauth or header. For OpenCode specifically that means: remote server entry in opencode.json. Once it loads, OpenCode can publish and schedule to X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest from a plain-language prompt.
04 What is the best way to manage social media with OpenCode?
Let OpenCode do the drafting and decision making, and let a publishing layer hold the accounts and the schedule. The thing that makes this work on OpenCode in particular: OpenCode is the only client here that can negotiate OAuth automatically through dynamic client registration, so it completes an OAuth setup with no application registered in advance and no key pasted anywhere. It also scopes servers two ways, globally or per agent, so a publishing agent can hold the Blotato tools while your coding agents never see them, and pairing that with its model-per-task switching lets you draft captions on one model and run the publish call on another.
05 What goes wrong when connecting OpenCode?
OpenCode is model agnostic, and that is where the friction usually is. The connection can be perfect while the model you selected handles tool calling poorly, which looks like a broken server but is a model choice. If the tools are listed and simply are not called, change the model before re-checking the config. Note also that MCP tools enter the context window, so a server with a large surface competes with your actual prompt for room.
06 Does OpenCode need to be running for a scheduled post to go out?
No. Scheduling runs on Blotato rather than inside OpenCode. Once the agent queues a post, it publishes at the scheduled time whether or not OpenCode, your terminal, or your laptop is on. This is the practical difference between an agent that drafts and a system that runs unattended.
07 What can I ask OpenCode to do once it is connected?
"Draft the captions on the cheap model, then publish." OpenCode configures a model per agent and lets you switch agents mid-session, so drafting can run somewhere inexpensive while blotato_create_post fires from whichever agent holds the tools. The publish call costs the same either way. "Keep these tools away from my coding agents." Scope the server to one agent rather than globally. A publishing agent holds the Blotato tools and the coding agents never see them, which also keeps 28 tool definitions out of their context window. "Turn this YouTube video into posts." blotato_create_source extracts the content and blotato_get_source_status polls until it resolves, then the text feeds blotato_create_post.
08 How much does it cost to connect OpenCode?
Starter is $29/mo flat for 20 connected accounts, and the price does not scale with posting volume. API and MCP access is not part of the 7-day trial: generating a key activates the paid Starter plan, so plan on subscribing rather than trialing it.

Connecting a different agent?

Same endpoint, same accounts, one setup per client. The AI agents for social media hub covers what all of them share, including every tool your agent can call.