Connect Microsoft Forms to Claude Code

Have Claude pull and summarize Microsoft Forms responses. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Microsoft Forms to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Microsoft Forms, you add a Microsoft Forms MCP server: a small hosted service that exposes Microsoft Forms's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Microsoft Forms account. No API keys pasted into config files.

claude mcp add --transport http microsoft-forms https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Microsoft Forms once connected?

A custom Microsoft Forms connector lets Claude pull submitted responses, summarize sentiment and themes, flag outliers, and draft a recap you can share. Microsoft Forms does not offer a public API to create or edit forms, so the connector concentrates on the response work that used to mean exporting to a spreadsheet by hand.

Pull and summarize submitted responses for a chosen form
Surface themes, sentiment, and outliers across open-text answers
Draft a recap or summary of results you can share with a team
Compare response counts and trends across forms over time
Export a clean, structured view of responses for further analysis
Flag submissions that match criteria you describe for follow-up

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Microsoft Forms access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Microsoft Forms API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Microsoft Forms changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Microsoft Forms connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Microsoft Forms connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Microsoft Forms account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Microsoft Forms's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Microsoft Forms?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Microsoft Forms account it signs in with. Revoking access is one click in Microsoft Forms.

More on the Microsoft Forms connector

Microsoft Forms connector for claude.ai SurveyMonkey + Claude Code Tally + Claude Code Formstack + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us