How to Use Microsoft Teams Transcripts With Claude: MCP Setup Guide (May 2026)
Learn how to connect Microsoft Teams transcripts to Claude using MCP servers. Skip manual exports and query your last 100 meetings instantly. May 2026 guide.
Maintouch
Teams transcripts and Claude don’t connect well when you’re doing it manually. You’ll wait hours for the recording to process, download a messy .vtt file if you’re lucky enough to be the organizer, then reformat everything before Claude can do anything useful with it. The better setup is an MCP server that feeds Claude your entire Teams meeting history on demand—and since Microsoft Teams has no native MCP server, Spinach bridges the gap by capturing every call automatically and exposing your last 100 meetings to Claude, ChatGPT, and Cursor through a single OAuth connection.
TLDR:
- Teams transcripts require organizer permissions and 1-24 hour processing delays before manual export
- Microsoft Teams has no native MCP server; third-party options need IT-level Graph API permissions
- Spinach MCP server connects your last 100 Teams meetings to Claude, ChatGPT, and Cursor via OAuth
- Query meeting context across multiple calls without manual uploads or reformatting
- Spinach records Teams meetings by default and exposes transcripts to AI tools through a centralized MCP endpoint
How to Export Microsoft Teams Transcripts for Claude
Getting Teams transcripts into Claude manually requires the right permissions and some patience. Only the meeting organizer or co-organizer can turn on transcription during a call, so regular attendees won’t have download access.
After your meeting wraps, plan to wait. Microsoft typically takes 1 to 24 hours to process the transcript. Depending on your organization’s settings, the file may be saved to SharePoint or directly within the Teams meeting recap tab.
Steps to Export Your Transcript
Once processed, here is how to get it out:
- Open the meeting in your Teams calendar and go to the recap tab, where you can download the transcript as a
.vttor.docxfile. - Copy the text content and paste it directly into a Claude conversation, or upload the
.docxfile if your Claude plan supports file uploads.
Why Manual Teams Transcript Workflows Create Friction
Raw Teams transcripts rarely arrive clean. They come packed with formatting artifacts, timestamps, and inconsistent speaker tags when you copy-paste into Claude, realistically costing you 15 to 20 minutes of reformatting before any analysis can begin.
Speaker attribution compounds the problem in larger calls. When people talk over each other or display names appear inconsistently, Claude ends up working with ambiguous data that weakens every insight it produces.
The deeper issue is isolation. Each transcript is a standalone file. Claude has no way to connect last week’s planning call with today’s follow-up, so you’re feeding it fragments instead of a continuous picture of meeting notes and what your team has decided.
Understanding Microsoft Teams MCP Server Limitations
Microsoft Teams has no native MCP server. MCP (Model Context Protocol) lets AI assistants like Claude pull live context from external apps without manual uploads. If Teams had native support, querying your transcripts in Claude would be as simple as asking a question.
Third-party MCP implementations built on the Microsoft Graph API do exist, covering messaging and channel management. Transcript access sits outside that scope, though. Pulling meeting transcripts via Graph API requires organization-wide admin permissions and a multi-step OAuth setup, meaning your IT team has to get involved before a single transcript reaches Claude.
How Model Context Protocol Powers Claude Integrations
MCP is an open standard that builds secure, two-way connections between data sources and AI tools like Claude. Instead of manually feeding Claude files, an MCP server exposes your data through a standardized interface that Claude can query on demand.
For meeting transcripts, that shift matters. Claude stops being a passive document reader and becomes an active participant in your workflow. Ask it what was decided in last Thursday’s call, who owns which action item, or what risks came up across three separate planning sessions, and it pulls answers directly from the source.
Spinach AI MCP Server: Direct Teams Transcript Access for Claude
Spinach fills the gap Teams leaves open. Connect your Microsoft Calendar to Spinach, and it automatically joins your Teams meetings, captures the full transcript using meeting note software, and stores everything in a centralized repository tied to your account.
The Spinach MCP server at https://mcp.spinach.ai/mcp exposes your last 100 meetings to Claude through a single OAuth connection. No repeat uploads, no reformatting. Once connected, Claude gets read-only access to:
- Full meeting transcripts with speaker attribution
- AI-generated summaries and action items
- Action items with assignees
- Participant lists across your meeting history
One setup. Every Teams call, queryable.
Setting Up Spinach MCP Connection in Claude Desktop
The setup takes under two minutes in Claude Desktop.
Here is how to get connected:
- Open Claude Desktop and go to Settings
- Select Integrations, then click Add Integration
- Name it “Spinach AI”
- Enter the MCP Server URL:
https://mcp.spinach.ai/mcp - Choose OAuth as the authentication method
- Authorize with your Spinach account
Once connected, Claude has access to your last 100 meetings and you can query them instantly. Try something like:
@spinach What decisions were made yesterday with engineering?
No file prep, no reformatting. Just ask.
Connecting Spinach to ChatGPT, Cursor, and VS Code
Claude Desktop is just one entry point. Spinach’s MCP server works across any MCP-compatible tool using the same endpoint and OAuth flow.
ChatGPT
Go to Settings > Integrations, turn on developer mode, and add a custom connector pointing to https://mcp.spinach.ai/mcp. Authorize with your Spinach account and you’re done.
Cursor and VS Code
Add the following block to your mcp.json configuration file:
{
"spinach": {
"url": "https://mcp.spinach.ai/mcp",
"type": "oauth"
}
}
Restart your editor, authorize once, and your last 100 meetings are available across all your AI assistants and coding agents.
Querying Teams Meeting Context Through Claude
Specificity drives better results. The more context you give Claude, the sharper the retrieval.
Prompts worth building into your workflow:
- “What action items were assigned to me in meetings this week?”
- “Summarize everything discussed about the Q3 roadmap across the last month of calls.”
- “What objections came up in Tuesday’s call with the product team?”
- “Pull key decisions from my last three syncs with engineering before my standup today.”
For cross-meeting analysis, name a time range and a topic. For single-meeting lookups, include the date and at least one participant name or project keyword. You can also ask Claude to draft follow-up emails, extract open action items by assignee, or flag recurring blockers across sessions.
Why Spinach Outperforms Manual Teams Transcript Workflows
The gap is structural, not procedural.
| Manual Teams Export | Spinach | |
|---|---|---|
| Meeting coverage | Organizer-only | Full calendar, recorded by default |
| Claude output | Raw transcript file | Summaries, action items, speaker attribution |
| Query style | Per-upload batch | Live, cross-meeting retrieval |
| Repository | Scattered local files | Searchable org-wide history |
| Setup frequency | Every meeting | Once |
You stop losing meetings you attended but didn’t run. Coverage becomes automatic, not opt-in.
Spinach AI: Meeting Intelligence Infrastructure for Claude and Beyond
Spinach captures every Teams meeting by default, then routes that data wherever your team works: CRMs like HubSpot and Salesforce, ticketing tools like Jira and Linear, and knowledge bases like Confluence, Notion, and Google Drive. APIs and webhooks handle custom workflows from there.
AskSpinach analyzes up to 20 meetings at once, giving leadership cross-functional visibility that per-meeting tools can’t match. Spinach is SOC 2, GDPR, and HIPAA compliant, so regulated teams can deploy with confidence. Usage-based pricing keeps costs manageable for teams under 100, while enterprises get full admin controls and private cloud options.
Final Thoughts on Accessing Teams Meeting Context in Claude
Manual downloads break down when you need context across multiple calls. Spinach records every meeting, structures the data, and feeds it to Claude through MCP so you can query decisions, action items, and discussion threads without touching a single file. Your meetings become a knowledge base Claude can read. Get Spinach running with Claude and stop uploading transcripts one at a time.
Yes. Connect Spinach AI’s MCP server to Claude Desktop, and your last 100 Teams meetings become queryable instantly—no downloading, reformatting, or file uploads required.
Manual export requires organizer permissions, 1-24 hour processing delays, and file reformatting before Claude can analyze anything. Spinach captures every Teams call you attend automatically and feeds clean transcripts directly to Claude through MCP, ready to query in seconds.
MCP is an open standard that connects data sources directly to AI tools like Claude. Instead of uploading files manually, Claude pulls your Teams meeting history on demand, turning it from a passive document reader into an active assistant that answers questions across your entire conversation history.
Open Claude Desktop, go to Settings > Integrations > Add Integration, enter `https://mcp.spinach.ai/mcp` as the server URL, choose OAuth authentication, and authorize your Spinach account. Setup takes under two minutes and gives Claude access to your last 100 meetings.
Yes. The same MCP endpoint (`https://mcp.spinach.ai/mcp`) connects to ChatGPT, Cursor, VS Code, and any MCP-compatible tool using OAuth authentication, giving all your AI assistants and coding agents access to your Teams meeting context.
Yes, once you connect Spinach’s MCP server to Claude. You can query up to 100 meetings at once by asking Claude to analyze context across specific time ranges or topics, like “summarize all product roadmap discussions from the last three weeks.” Manual Teams exports only give you one transcript at a time with no way to connect conversations.
No. Spinach’s MCP server uses OAuth authentication tied to your personal account, so you only need permission to attend meetings—not IT-level Graph API access. You authorize once in Claude Desktop and your last 100 meetings become queryable without involving your admin team.
Ask Claude time-bound queries with specific assignees, like “what action items were assigned to me in meetings this week?” or “show all open tasks from product syncs in March.” Spinach’s MCP server feeds Claude structured action items with assignees and due dates, so you get clean task lists instead of raw transcript searches.
Spinach makes transcripts available to Claude within minutes of your meeting ending. There’s no 1-24 hour processing delay like manual Teams exports, and you never lose access to meetings you attended but didn’t organize.
Spinach’s MCP server requires OAuth and connects in under two minutes with read-only meeting access. Microsoft Graph API requires organization-wide admin permissions, multi-step OAuth setup, and custom code to format transcript data before Claude can use it. Spinach handles recording, formatting, and MCP exposure automatically.
Yes, when you use Spinach. Manual Teams exports only work for organizers, but Spinach records every meeting on your calendar automatically and exposes all of them through MCP. Claude gets the full context of meetings you attended, even if someone else sent the invite.
Your transcripts stay accessible. Spinach’s MCP server uses the same endpoint for Claude, ChatGPT, Cursor, and VS Code, so you authorize once per tool and all of them pull from your centralized meeting history. No re-uploads or reformatting when you switch AI assistants.
Spinach captures speaker attribution during the live meeting and structures it before Claude sees the transcript. Raw Teams exports often have inconsistent display names and overlapping dialogue markers that require manual cleanup before Claude can identify who said what.
Yes. Add Spinach’s MCP server to your Cursor or VS Code config file using OAuth authentication, and your coding agents get context from your last 100 Teams meetings on demand. This turns meeting decisions into inline context for code generation without leaving your editor.
Yes, but Spinach handles this automatically. When you connect your Microsoft Calendar to Spinach, it joins and records your Teams meetings by default, then exposes those transcripts to Claude through MCP. Manual workflows depend on organizers remembering to enable recording each time.
What to do next
You made it to the end of this article! Here are some things you can do now:
- Our library of meeting agenda templates is designed to help you run more effective meetings.
- Learn more about Spinach and how it can help you run a high performing org.
- If you found this article helpful, please share it with others on Linkedin or X (Twitter)
