Skip to main content
Use ChatSyncs from GitHub Copilot Chat inside Visual Studio Code.

Before you start

  • VS Code with GitHub Copilot signed in. Copilot Free is enough.
  • Copilot Business or Enterprise? Your organisation’s admin must enable the MCP servers in Copilot policy (it’s off by default for those plans). If your organisation restricts MCP to an approved registry, ChatSyncs must be allowed there too.
  • Your ChatSyncs API key, from the API Developer Console. How to find it.

Connect

1

Start the Add Server command

Open the Command Palette (Cmd + Shift + P on Mac, Ctrl + Shift + P on Windows), type MCP: Add Server, and press Enter.
2

Answer the prompts

  • Server type: choose HTTP.
  • URL: paste
  • Server ID / name: chatsyncs
  • Where to save it: choose Copilot Global to use it in every project. (Choosing .mcp.json saves it for the current project only.)
3

Trust and sign in

VS Code asks whether you trust the server: confirm. It then asks to let chatsyncs sign in: click Allow. The ChatSyncs connect page opens in your browser. Paste your API key and click Authorize, then return to VS Code.
4

Find the tools in chat

Open Copilot Chat and click the Configure Tools button in the chat box. The ChatSyncs tools are listed and switched on.

Check it worked

In Copilot Chat, ask:
“List my WhatsApp templates.”
Copilot shows the ChatSyncs tool it wants to run and asks you to allow it, then lists your templates.

Disconnect

Run MCP: List Servers from the Command Palette, select chatsyncs, and choose Disable to pause it, or Uninstall to remove it. You can also right-click it under MCP SERVERS - INSTALLED in the Extensions view. To cut off every app that has your key, regenerate it.

Frequently asked

Yes, and VS Code can ask for the key and store it securely rather than in the file. This works in VS Code’s own Copilot Chat; Agent Host sessions don’t support it, so use browser sign-in there. Run MCP: Open User Configuration and paste:
The first time ChatSyncs starts, VS Code asks for the key. Paste only the key: VS Code adds the Bearer part itself. If the file already has content, merge in the inputs and servers parts instead of replacing it.
Save it to .mcp.json in the project and commit that file. Each person signs in with their own key. Never put a key itself into a shared file.
Your Copilot Business or Enterprise admin needs to enable the MCP servers in Copilot policy on GitHub and, if MCP is limited to a registry, allow ChatSyncs.

Gotchas

  • No ChatSyncs tools in chat. The server isn’t running or isn’t trusted. Run MCP: List Servers, pick chatsyncs, and start it.
  • You clicked “Don’t trust” by mistake. Run MCP: Reset Trust and start the server again.
  • “ChatSyncs did not accept that key.” Copy the key again with no spaces around it.