Last updated: August 2026

Can Copilot post to X?

GitHub Copilot can, in VS Code agent mode, once you add an MCP server to .vscode/mcp.json and approve the tool call. Copilot itself has no X access. Microsoft 365 Copilot is a different, admin-gated product. Neither posts unattended, so schedule rather than publish for anything time-based.

Three products share the name and only one of them has a clean answer. Sort out which Copilot you mean first, then the setup is a single config file.

Which Copilot do you mean?

Product

Can it post?

How

GitHub Copilot in VS Code

Yes, with an MCP server

Add the server to .vscode/mcp.json, use Copilot Chat in agent mode, approve the tool call. This is the answer most people are looking for.

GitHub Copilot coding agent

Yes, where MCP is permitted

It can use configured MCP servers while working on a repository. Treat any write tool here carefully: the agent is acting on issue and PR text it did not write.

Microsoft 365 Copilot

Only via tenant connectors

Different extensibility model, controlled by your workspace admin. If a connector is not published for your tenant, an individual user cannot add one.

Copilot in GitHub Actions

Not the right tool

CI has no chat session to approve a tool call. Call the REST endpoint directly from a workflow step with a repository secret.

The VS Code setup, end to end

VS Code reads MCP servers from a workspace file. Add one entry, restart, and the tools appear in Copilot Chat when you switch to agent mode.

.vscode/mcp.json

{
  "servers": {
    "opentweet": {
      "type": "http",
      "url": "https://mcp.opentweet.io/mcp",
      "headers": { "Authorization": "Bearer ot_your_key" }
    }
  }
}

Then open Copilot Chat, pick agent mode, and ask for what you want. The posting, threading and scheduling tools show in the tool picker, and each write pauses for your approval before it runs.

Tools not appearing? Fully quit and reopen VS Code. A window reload is not always enough, the config is read at startup.
Wrong mode? Ask mode and edit mode do not call tools. It has to be agent mode.
No Copilot subscription? MCP in VS Code runs through Copilot Chat. Cline is an alternative extension with its own MCP client and the same server config.

Per-editor notes are in the MCP docs, with client pages for VS Code, Copilot and Cline.

The thing agent mode cannot do

Copilot only acts while you are there. Agent mode shows the tool and its arguments and waits for approval, which is the correct default when the model can be influenced by whatever file or issue it just read. It also means there is no version of this that posts your release note at merge time while you are asleep.

Two ways to work with that rather than against it. Have the agent schedule instead of publish, so you approve once and the post goes out later on its own. Or move the time-based part into CI, where no approval step exists because no session exists.

.github/workflows/announce.yml

- name: Announce the release
  run: |
    curl -sS -X POST https://opentweet.io/api/v1/posts \
      -H "Authorization: Bearer $OPENTWEET_KEY" \
      -H "Content-Type: application/json" \
      -d "{\"text\": \"Shipped ${{ github.ref_name }}.\", \"publish_now\": true}"
  env:
    OPENTWEET_KEY: ${{ secrets.OPENTWEET_KEY }}

The full workflow, including tagging and failure handling, is in post to Twitter from GitHub Actions. If you want the agent to keep the decision but not the timing, read API vs MCP for posting.

A write tool inside a coding agent deserves a second look

The coding agent reads issues, pull request descriptions and repository files, any of which can be written by someone else. Giving it a tool that publishes to your account means that text is now one step from your timeline. Prefer scheduling over publishing there, so a human sees the queue before anything goes live. More on this in is it safe to connect an MCP server to my X account.

7-day free trial. Cancel anytime.

Frequently asked questions

Can Copilot post to X?

GitHub Copilot can, in VS Code agent mode, once you add an MCP server that exposes a posting tool to .vscode/mcp.json and approve the tool call. Copilot on its own has no connection to your X account. Microsoft 365 Copilot is a separate product with admin-gated connectors and is not the same answer.

Which Copilot are we talking about?

Three different products share the name. GitHub Copilot in your editor, which supports MCP servers in agent mode. GitHub Copilot coding agent, which runs work on a repository. And Microsoft 365 Copilot in Word, Outlook and Teams, which uses a different extensibility model that your tenant admin controls. Only the first is a straightforward yes.

How do I add an MCP server to GitHub Copilot in VS Code?

Create .vscode/mcp.json in your workspace, add the server under the servers key, then open Copilot Chat and switch to agent mode. The new tools appear in the tool picker. Restart VS Code fully if they do not show up, since the config is read at startup.

Do I need a GitHub Copilot subscription for MCP in VS Code?

Yes. MCP tool use in VS Code runs through Copilot Chat in agent mode, so it needs an active Copilot entitlement. If you would rather not add one, extensions such as Cline bring their own MCP client and work with the same server configuration.

Will Copilot post without asking me?

No. Agent mode surfaces the tool call and its arguments for confirmation before a write runs. That makes it a good fit for publishing while you work and a poor fit for anything that must happen at a fixed time. For time-based posting, have the agent schedule rather than publish, or call the REST endpoint from CI.

Can Copilot post a release note when I merge a pull request?

Not by itself, because that happens when nobody is in the editor. Put that in a GitHub Actions step that calls POST https://opentweet.io/api/v1/posts with a repository secret. Copilot is useful for writing the workflow and the copy, not for being the thing that fires at merge time.

Keep exploring

Post to X from your editor, your agent, or your CI. Same key for all three.

OpenTweet vs the X API

Post, schedule, and automate X without a developer account or the $200/mo minimum.

X DM outreach, human-approved

Find and qualify leads, AI-draft DMs, approve each one, and drip-send from your own account via API or MCP.

Post to X without an API

The clean, account-safe way to post to X from your code or an AI agent.

Twitter MCP Server

Give Claude, Cursor, and OpenClaw the ability to post to X. 36 tools included.

Developer docs

Quickstart, API keys, MCP setup, and the REST reference for posting to X from code or an agent.

XMCP vs OpenTweet

X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.

MCP for AI agents

Connect your AI client to X in under two minutes, no X developer account.

Developer API and keys

REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.

OpenTweet for AI agents

The posting layer for autonomous agents and automations that live on X.

Build an AI Twitter persona

Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.

Best MCP servers for social media

The 2026 ranked list. How the hosted OpenTweet MCP compares with the official X MCP and others.

Cheapest way to post to X via code

Flat fee vs pay-per-use. Why the $0.20 per-link fee flips the math past ~60 posts a month.

Give Copilot a posting tool

One entry in .vscode/mcp.json and agent mode can post, thread and schedule. Flat $11.99 a month, no X developer app.

7-day free trial. Cancel anytime.