Schedule social media posts with VS Code with GitHub Copilot
Add Postozo to VS Code as an MCP server. Then use Copilot chat to write, check and schedule posts without leaving your editor.
How to connect Postozo to VS Code with GitHub Copilot
You need a Postozo account with at least 1 connected channel. VS Code with GitHub Copilot connects to Postozo's MCP server at https://app.postozo.com/mcp using OAuth sign-in or an API key header.
Option 1: guided. Open the Command Palette, run MCP: Add Server, follow the prompts to add an HTTP server with the URL https://app.postozo.com/mcp, and pick Workspace or Global. When VS Code asks, sign in to Postozo and click Allow. VS Code supports automatic client registration for OAuth.
Option 2: API key in a file. In Postozo, open Settings, Developers and copy your API key. It starts with pz_live_. Treat it like a password. Create .vscode/mcp.json:
{
"inputs": [
{ "type": "promptString", "id": "postozo-key", "description": "Postozo API key", "password": true }
],
"servers": {
"postozo": {
"type": "http",
"url": "https://app.postozo.com/mcp",
"headers": { "Authorization": "Bearer ${input:postozo-key}" }
}
}
}VS Code asks for the key the first time and stores it safely, so the file can be shared. Then open Chat, use Configure Tools to turn on the Postozo tools, and ask: "List my Postozo channels".
Your organisation's GitHub Copilot policy can turn MCP servers off. Ask your admin if the server does not appear.
Check it works
In Chat, ask: "List my Postozo channels."
What VS Code can do with Postozo
Postozo gives VS Code 20 tools. A normal flow is: list your channels, read the rules of each network, check the post, find a free slot, then schedule it once you say yes.
| Tool | What it does | Changes data |
|---|---|---|
list_channels | List the connected social channels (accounts, pages) with their id, network, name and status. Call this first to get channel ids. | No |
list_networks | List every network this server supports and whether it can be connected. Useful to explain what is possible. | No |
list_customers | List customers. A customer groups channels (agencies use 1 per client). | No |
get_channel_rules | Get the posting rules for 1 channel: max length, media needs, whether comments are supported, and the settings schema (some settings are required, for example a title on YouTube or a board on Pinterest). Read before scheduling to that channel. | No |
find_free_slot | Find the next free posting time for these channels, using each channel's preferred posting times. | No |
check_post | Check a post against every channel's rules without saving it. Returns a list of problems (empty means it is fine). | No |
schedule_post | Create or edit a post for 1 or more channels. Supports drafts, scheduling, posting now, client review, threads with delays, per-channel text, network settings, tags and repeats. Returns the post id, its status and a preview link. | Yes |
list_posts | List posts on the calendar between 2 dates (default: last 7 days to next 30 days). | No |
get_post | Get 1 post with its text per channel, state per channel (queued, published, error...), links to the live posts, errors with a fix, comments and history. | No |
change_post_date | Move a post to a new date and time. | Yes |
retry_post | Retry the channels of a post that failed or could not be confirmed. Only use after the user confirms the post is not already live. | Yes |
delete_post | Delete a post from the calendar. Posts already live on a network stay live there. | Yes |
upload_media_from_url | Import an image or video from a public URL into the media library. Returns a media id to use in schedule_post. | Yes |
list_media | List files in the media library. | No |
list_tags | List tags used to label posts. | No |
get_analytics | Get account statistics for 1 channel from its network (7, 30 or 90 days). Some networks do not share statistics. | No |
get_post_analytics | Get statistics for 1 published post on 1 channel. Use the per-channel post id from get_post (channels[].root.id). | No |
get_workspace_stats | Counts from this workspace: posts by state, published posts per channel, and short link clicks. | No |
run_channel_tool | Run a network helper for 1 channel, for example list Pinterest boards, Reddit flairs or YouTube playlists, to fill a setting. get_channel_rules lists the tools for each channel. | No |
generate_image | Create an image with AI from a description and save it to the media library. Uses 1 image credit. Returns a media id. Only when AI images are turned on for your workspace. | Yes |
The server also offers 2 ready prompts: plan_week (plan 5 posts for the next 7 days about a topic) and repurpose (turn a link or text into 1 post per channel).
Example prompts
- "Write a LinkedIn post about the feature in this file and check it against the LinkedIn rules."
- "Draft release notes for Discord and Slack from the last tag."
- "Schedule the draft for Thursday 11:00 on LinkedIn and X."
- "List posts that failed and explain each error."
- "Find a free slot for my Instagram channel this week."
- "Save this as a draft and send it for approval."
Safety and control
- 14 of the 20 tools only read. The 6 that change data (schedule_post, change_post_date, retry_post, delete_post, upload_media_from_url and generate_image) are marked as write tools, so VS Code can ask you before it runs them.
- The server tells the AI to confirm the text, channels and time with you before it schedules or publishes.
- Ask for drafts ("save as drafts") or for client review ("send for approval") when you want a human to check first.
- A post is never sent twice. If Postozo cannot confirm a post went live, it marks it "could not confirm" instead of retrying on its own.
- Remove access any time in Postozo under Settings, Approved Apps, or by creating a new API key.
Sources
Questions
Can VS Code with GitHub Copilot schedule posts with Postozo?
Yes. After you add Postozo's MCP server, VS Code with GitHub Copilot can list your channels, check each network's rules, find free times and create drafts, scheduled posts or posts for client approval.
Where do I see the tools?
In the Chat view, open Configure Tools and turn the Postozo tools on.
Is the key saved in the file?
No. With the inputs block, VS Code asks for it once and stores it outside the file.
Can I use it for all projects?
Yes. Run MCP: Open User Configuration and add the same server there.
Does it cost extra?
No. The API and MCP server are included in every Postozo plan. VS Code with GitHub Copilot has its own plans and limits.
Connect VS Code with GitHub Copilot to Postozo
Start a 7-day free trial, connect your channels, then add the server.
Create your free account