How to let an AI assistant schedule your GitHub merges, safely

AI coding assistants already open pull requests for you. The next step is asking them to get the change live: "schedule PR 42 for 11 pm tonight". With the Model Context Protocol (MCP), an assistant can call tools on another service, so this is possible today. It is also a way to ship something you did not mean to, so the setup matters.

What can go wrong

A safe setup

How Merge Scheduler's MCP server does it

The server uses the same API keys as the REST API, and a key acts as the person who made it. A read key sees only the read tools. Nothing exposed to an assistant can change repo rules, billing, members or keys. Scheduling refuses what the app refuses, so a pull request that needs an approving review comes back with the reason instead of being scheduled. Times without a UTC offset are refused, the commit is pinned, and every call is listed in the workspace's API activity.

Connecting one

Clients that only connect through a sign-in page cannot use the server yet. Setup differs by client, so check your assistant's current instructions.

Prompts that work well

Do this in Merge Scheduler: Schedule merges from the API or an AI assistant

Related: How to release stacked pull requests safely · Why a scheduled merge should pin the commit you approved