GitHub MCP Connectors Come to Copilot: 26 Verified Servers and What They Mean for the Forms Your Agent Builds (2026)

GitHub MCP connectors are now in public preview for every Copilot plan. On October 28, GitHub announced GitHub-verified MCP servers, which it also calls connectors: 26 services you can connect to Copilot with one sign in, and nothing to find or install.

That matters beyond GitHub. When the biggest coding assistant makes MCP a one-click thing, the protocol stops being a power-user feature. Here is what shipped, who controls it, and what it means for the forms your agent builds.

What GitHub shipped

The pitch is in the changelog title: connect your tools to Copilot "without all the setup". You pick a service, sign in, and Copilot keeps you signed in in the background. According to GitHub, a service you connect in one place works everywhere: the Copilot app, Copilot CLI, VS Code, Copilot in the cloud and GitHub Mobile.

At launch there are 26 services. GitHub names Slack, Figma, Notion, Sentry, Linear, Atlassian Rovo, Cloudflare, Vercel and Work IQ among them. Where you connect them depends on the surface. In the Copilot app, it is Customize. In the CLI, it is the /mcp command and its Connectors tab. In VS Code, it is Customizations, and on github.com, the Copilot customization page.

Who controls the GitHub MCP connectors

For individuals, the connectors are simply there. For companies, there are three switches:

• The preview policy. On Copilot Business or Enterprise, an admin first enables the "Editor preview features" policy.
• The MCP allowlist. If the enterprise uses an MCP allowlist, an admin adds the GitHub-verified servers to it.
• The service itself. Some services also need an admin on their side, for example to allow Slack MCP access.

In other words, the GitHub MCP connectors make MCP easier to turn on, not harder to govern. That is the right order for a company that wants agents to touch real tools.

What it means for the forms your agent builds

MCP is how an agent reaches a tool without a custom integration. Connectors like these teach millions of developers to expect it: you sign in once, and the agent can act. The next question every team asks is which of their other tools work the same way.

Forms are one of them. dForms is the form builder for AI agents, and it ships its own MCP server at https://mcp.dforms.ai/mcp, with OAuth sign in. Through it, an agent can create a form, publish it, read every response with its score and send the hot leads to HubSpot or a webhook.

To be clear, dForms is not one of the 26 verified connectors. However, Copilot in VS Code also lets you add your own MCP servers, including remote servers with OAuth, as GitHub's documentation on extending Copilot Chat with MCP explains. The dForms server is the same one that Claude, Claude Code and Cursor use, as our guide on how to create a form with Claude shows. We have not tested it inside Copilot yet, so treat that path as untested for now.

There is also a lesson in GitHub's controls. As more agents act through MCP, the question shifts from "can it connect?" to "who approves what it does?". We covered that shift when Claude made auto mode the default.

Try it with dForms

In Claude, add the dForms connector at https://mcp.dforms.ai/mcp and sign in. If you would rather script it, create a dForms API key on the Developers page. Then give your agent its first form:

Create a form in dForms called "Bug report" with:
your email, which app (web / mobile / API), what happened (open text),
how often it happens (once / sometimes / every time),
and a screenshot upload.
Give "every time" the most points so the worst bugs sort to the top.
Leave it as a draft and send me the preview link.

Your agent builds the form and its scoring, and once you publish it, it can read every report sorted by score.

Frequently asked questions

What are GitHub MCP connectors?

GitHub MCP connectors are GitHub-verified MCP servers that Copilot can use after one sign in. At launch there are 26, including Slack, Figma, Notion and Sentry, in public preview on all Copilot plans.

Is dForms one of the GitHub MCP connectors?

No. dForms is not among the 26 verified servers. It has its own MCP server with OAuth that works in Claude, Claude Code and Cursor; we have not tested it in Copilot yet.

Do companies need to turn the connectors on?

Yes, on Copilot Business and Enterprise. An admin enables the "Editor preview features" policy and, if the enterprise uses an MCP allowlist, adds the verified servers to it.