Let GitHub Copilot in VS Code schedule your posts

Copilot agent mode plus a social calendar

Copilot's agent mode can call tools from MCP servers. Postika gives it five: list_projects, list_channels, list_posts, create_post and delete_post. That is enough for the usual developer marketing loop: read what you shipped, write about it, put it on the calendar, and check nothing else is going out the same day.

Because it runs inside the editor, Copilot can use the file you have open as the source. A good habit for open-source maintainers is to ask for a post right after writing release notes, while the details are fresh. The MCP glossary page explains how remote servers like Postika work.

Sharing the setup with your team

Committing .vscode/mcp.json means every contributor who opens the repo gets the Postika server configured. Each person still signs in with their own Postika account through OAuth, so nobody shares a password or token in the repository.

If several people announce the same product, one Postika project with the product's channels keeps everything on one calendar in one time zone. Posts created by Copilot arrive as pending approval, so the maintainer who owns the accounts decides what goes out. Read more in the approval workflow entry. Postika is priced by connected channels, not by seats (pricing).

Network rules Copilot gets from Postika

list_channels returns the limit and media rule of each channel, and create_post is rejected if a post breaks them. For developer audiences the common networks are:

Screenshots and videos are added in the Postika app because MCP does not carry files. Postika does not create X threads. For automation outside the editor, use the REST API or see Postika for developers and Cursor.

Typical uses for open-source and product teams

• Release day: after writing the release notes, ask Copilot for an X, Threads and LinkedIn version, pending approval at the time you usually announce.
• Docs launches: with a new guide open in the editor, ask for a post that links to it, as a draft for the docs owner to review.
• Contributor thanks: list the merged PRs of the month and write a LinkedIn post thanking contributors by handle.
• Calendar check: before a launch, ask what else is scheduled in the project for that week, so a big announcement does not compete with a minor one.

All of these are text-first, which is where the MCP flow is fully automatic.