GitHub Copilot and Postfjord

What it does

GitHub Copilot can work in Postfjord from Copilot Chat in VS Code or from the Copilot CLI in your terminal. Ask it to check your calendar, plan a week of posts or write drafts in your brand voice. It connects with a key, and you decide what the key may do.

It is included from the Solo plan, and only the workspace owner can make keys.

Connect in three steps

1. In Postfjord, open Settings, Apps and press the GitHub Copilot card. Make a key and copy it.
2. In VS Code, add Postfjord to .vscode/mcp.json with the address https://mcp.postfjord.com/mcp and the header Authorization: Bearer followed by your key. In the Copilot CLI, run copilot mcp add with the same address and header.
3. Open Copilot Chat, pick Agent, and check that the Postfjord tools are in the tools list.

What moves where

• From Postfjord to Copilot: what the key's level allows it to read, like your calendar, brand profile, post results and Inbox.
• From Copilot to Postfjord: the drafts it writes, and with the top level the posts it schedules.
• Revoke the key under Your keys and Copilot stops working in Postfjord at once.

FAQ

Which Copilot plan do I need?

Copilot Free, Pro, Pro+ and Max work as they are. On Copilot Business or Enterprise, an owner of the organization first sets MCP servers in Copilot to Enabled in the organization's Copilot policies.

Where are the full steps?

On the MCP help page, with the text to paste for VS Code and the Copilot CLI.