How to use X (Twitter) with Copilot Studio
You want X (Twitter) inside Copilot Studio so it can monitor conversations that need a response, track competitors and industry signals, publish an approved launch thread, and organize a list of relevant accounts — without you copy-pasting between tabs. Here is the whole setup, once.
Create your X (Twitter) gateway
The gateway is the thing Copilot Studio connects to, and it is where you decide which X (Twitter) tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your X (Twitter) tools
In the dashboard, create a gateway and pick the X (Twitter) tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Copilot Studio
Needs a Microsoft 365 subscription with access to Copilot Studio, plus an Arcade API key.
-
Add an MCP tool to your agent
In Copilot Studio, open your agent → Tools → Add a tool → Model Context Protocol → New tool.
-
Point it at your gateway
Give the server a name and description, put your gateway URL in Server URL, set Authentication to OAuth 2.0 and Type to Dynamic discovery.
-
Authorize and try it out
Saving redirects you to Arcade to approve access. Then start a conversation and use your X (Twitter) tools — Arcade authorizes each service just in time.
Full Copilot Studio guide in the docs steps verified 2026-08-13
Try these X prompts
Copilot Studio can now act on your X (Twitter) account. Click a prompt to copy it.
Require approval before an agent publishes, replies, retweets, likes, deletes posts, or changes lists. Pair it with Contextual Access policies so an agent can monitor conversations without being allowed to publish or delete posts.