GitHub Copilot

How to Post to Social Media From GitHub Copilot

GitHub Copilot agent mode reads MCP servers from an mcp.json file. Add a server with type set to http and url set to https://mcp.blotato.com/mcp, authenticate with either a blotato-api-key header or the oauth field, and Copilot can publish and schedule across nine platforms from the editor. Where you put that file matters more than usual here, because the workspace .vscode/mcp.json and the file the Agent Host reads are not the same path.

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

Updated August 2026

How to connect GitHub Copilot to social media

  1. Connect your social accounts in Blotato and copy your API key from Settings then API.
  2. Create a workspace .mcp.json, or a user-level ~/.copilot/mcp-config.json, which the Agent Host reads natively.
  3. Add the server under "servers" with type set to http, url set to https://mcp.blotato.com/mcp, and blotato-api-key in headers.
  4. Open the Chat view, switch to agent mode, and confirm the Blotato tools are listed in the tools picker before running anything against a live account.
workspace .mcp.json or ~/.copilot/mcp-config.json, read natively by the Agent Host
{
  "servers": {
    "blotato": {
      "type": "http",
      "url": "https://mcp.blotato.com/mcp",
      "headers": {
        "blotato-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Two different products carry this name. Copilot agent mode in VS Code is the one described here, and it accepts both OAuth and a header. Copilot cloud agent on github.com also takes remote MCP servers, but does not support OAuth for them and reads secrets from COPILOT_MCP_-prefixed variables instead, so a config that works in one is not guaranteed in the other.

How do I know it worked?

Ask GitHub Copilot 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 return data for every platform except LinkedIn, which publishes normally but reports no metrics yet.

What to ask GitHub Copilot once it is connected

Announce this pull request on X once I merge it.
blotato_create_post with the text drafted from the diff already open, so the announcement is written where the change is rather than retyped later.
Schedule these four posts across next week instead of firing them now.
blotato_create_post with a scheduled time per post, or useNextFreeSlot to drop them into the slots already configured. Scheduling runs on Blotato, so the posts go out with VS Code closed.
Reply to the comments on yesterday's Instagram post.
blotato_list_comments to read them, then blotato_post_comment per reply. Comments cover Instagram and Facebook.

What breaks, and how to fix it

The trap here is the one the VS Code docs flag themselves: servers requiring interactive input are not forwarded to the Agent Host, and ${input:...} variables count as interactive input. So the tidy pattern of routing an API key through an input variable is exactly what stops the server reaching the agent, and it fails by absence, with the server simply missing rather than erroring. The related path issue is that the Agent Host does not read .vscode/mcp.json directly, so a config that works in the chat panel can be invisible to the agent. Use a workspace .mcp.json or ~/.copilot/mcp-config.json with the key written literally, and keep that file out of version control.

What is different about GitHub Copilot

Two separate products ship under this name and they do not authenticate the same way. Copilot agent mode inside VS Code supports an oauth object on the server entry, so it can run the browser consent flow on first connection instead of holding a key at all. Copilot cloud agent on github.com also accepts remote MCP servers, but GitHub's docs state it does not support OAuth for them: the key goes in an Agents secret prefixed COPILOT_MCP_ instead, so a config proven in the editor is not automatically valid there. Worth knowing before you promise a teammate that the setup transfers.

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

FAQ

GitHub Copilot social media FAQs

01 Can GitHub Copilot post to social media?
Yes. GitHub Copilot 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. GitHub Copilot authenticates with oauth or header.
02 How do I connect GitHub Copilot to social media?
GitHub Copilot agent mode reads MCP servers from an mcp.json file. Add a server with type set to http and url set to https://mcp.blotato.com/mcp, authenticate with either a blotato-api-key header or the oauth field, and Copilot can publish and schedule across nine platforms from the editor. Where you put that file matters more than usual here, because the workspace .vscode/mcp.json and the file the Agent Host reads are not the same path.
03 How do I set up GitHub Copilot for social media?
Setting up GitHub Copilot for social media takes one connection. Connect your social accounts in Blotato, then give GitHub Copilot the hosted MCP endpoint https://mcp.blotato.com/mcp and authenticate with oauth or header. For GitHub Copilot specifically that means: workspace .mcp.json or ~/.copilot/mcp-config.json, read natively by the agent host. Once it loads, GitHub Copilot 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 GitHub Copilot?
Let GitHub Copilot do the drafting and decision making, and let a publishing layer hold the accounts and the schedule. The thing that makes this work on GitHub Copilot in particular: Two separate products ship under this name and they do not authenticate the same way. Copilot agent mode inside VS Code supports an oauth object on the server entry, so it can run the browser consent flow on first connection instead of holding a key at all. Copilot cloud agent on github.com also accepts remote MCP servers, but GitHub's docs state it does not support OAuth for them: the key goes in an Agents secret prefixed COPILOT_MCP_ instead, so a config proven in the editor is not automatically valid there. Worth knowing before you promise a teammate that the setup transfers.
05 What goes wrong when connecting GitHub Copilot?
The trap here is the one the VS Code docs flag themselves: servers requiring interactive input are not forwarded to the Agent Host, and ${input:...} variables count as interactive input. So the tidy pattern of routing an API key through an input variable is exactly what stops the server reaching the agent, and it fails by absence, with the server simply missing rather than erroring. The related path issue is that the Agent Host does not read .vscode/mcp.json directly, so a config that works in the chat panel can be invisible to the agent. Use a workspace .mcp.json or ~/.copilot/mcp-config.json with the key written literally, and keep that file out of version control.
06 Does GitHub Copilot need to be running for a scheduled post to go out?
No. Scheduling runs on Blotato rather than inside GitHub Copilot. Once the agent queues a post, it publishes at the scheduled time whether or not GitHub Copilot, 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 GitHub Copilot to do once it is connected?
"Announce this pull request on X once I merge it." blotato_create_post with the text drafted from the diff already open, so the announcement is written where the change is rather than retyped later. "Schedule these four posts across next week instead of firing them now." blotato_create_post with a scheduled time per post, or useNextFreeSlot to drop them into the slots already configured. Scheduling runs on Blotato, so the posts go out with VS Code closed. "Reply to the comments on yesterday's Instagram post." blotato_list_comments to read them, then blotato_post_comment per reply. Comments cover Instagram and Facebook.
08 How much does it cost to connect GitHub Copilot?
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.