Document & File Management · Castingwords + Claude
CastingWords MCP with Claude: Turn Audio Recordings into Searchable Transcripts
The short answer
Claude works with CastingWords through the Model Context Protocol (MCP), a secure standard that lets Claude use the tool with permissions you control. Once connected, Claude can upload audio files, check the status of transcription jobs, fetch finalised transcripts and manage the queue, all from plain-English instructions.
What is Castingwords?
CastingWords is a transcription service that produces accurate, human-checked transcripts of audio recordings. It offers a simple API, so software can send files and receive text back automatically. Teams use it for interviews, meetings, podcasts, research recordings and other spoken content that needs to become written text. Researchers, media producers, legal and HR teams, and operations staff are common users who need reliable transcripts without manual typing.
How Claude connects to Castingwords through MCP
The Model Context Protocol is an open standard that acts like a universal adapter between Claude and other software. It lets Claude securely read information from a tool and take actions in it, with the permissions your organisation decides on. For CastingWords, this means Claude can work with your transcription account in a controlled way rather than through copy-and-paste.
Once connected, Claude can typically upload new audio files, check whether a transcription job is in progress or complete, fetch finalised transcripts when they are ready, and review the transcription queue. Your team can make these requests in everyday language, such as asking which interview recordings from last week are still waiting to be transcribed.
Access is set up with a sign-in method supported by CastingWords, here an API key, and is limited to the actions your workflow needs. People stay in charge: consequential steps such as sending transcripts onward to clients or storing them in shared folders can require a person's approval, and every action can be recorded in an audit log.
What you can automate
Interview transcription for research teams
Researchers record interviews and ask Claude to upload each file as it arrives. Claude checks job status and fetches the finished transcript, so the team can begin coding responses without waiting for someone to chase the transcription provider. Staff spend their time analysing findings rather than managing files.
Podcast and media production
Producers upload episode recordings and ask Claude for the transcript once it is ready. The text can then be used for show notes, captions, searchable archives and quote extraction. Claude keeps a running view of which episodes are still in the queue, so the editorial calendar stays on track.
Meeting notes for operations and leadership
Important internal meetings can be recorded, uploaded and transcribed. Claude retrieves the finished transcript and prepares it for the relevant manager, who reviews it before any action is taken. This reduces the time spent writing minutes and helps teams keep an accurate record of decisions.
Legal and HR documentation
Legal and HR teams often need accurate records of recorded statements, hearings or exit interviews. Claude can track these jobs and fetch final transcripts into the correct restricted folder, with access limited to authorised staff. Human review remains part of the process before any transcript is relied upon.
Queue management and reporting
Managers responsible for many recordings can ask Claude for a plain-English summary of the transcription queue, including what is pending, what is complete and what needs attention. This gives operations leads a quick overview without logging in to the service each time.
An end-to-end workflow: Interview recordings to searchable research archive
TriggerA researcher drops a new interview recording into a shared project folder in Microsoft 365.
Claude detects the new audio file and uploads it to CastingWords through MCP.
Claude records the job reference and checks its status at regular intervals.
When the transcript is finalised, Claude fetches it from CastingWords.
Claude saves the transcript alongside the audio in the project folder and notifies the researcher.
The CRM or project tracker is updated with the interview date, participant code and transcript link, after the researcher approves.
OutcomeTranscripts are ready within the expected turnaround time without manual uploading or chasing. The research archive stays complete, searchable and consistently organised across the project.
How we set it up
Free automation audit
We review your recording and document workflows and identify where transcription is slowing your team down. You leave with a clear list of the workflows worth automating, at no cost.
Secure API key connection
We connect Claude to CastingWords using an API key, stored securely and limited to the actions your workflow requires. Access is granted with least-privilege permissions and can be revoked at any time.
Workflow design
We map the end-to-end process across CastingWords and your other systems, such as Microsoft 365, your CRM or your document store. Approval points are agreed for any step that shares or files transcripts.
Testing with real recordings
We run the workflow against past recordings to confirm that uploads, status checks and transcript retrieval behave as expected. Results are reviewed with your team before anything goes live.
Launch, monitoring and training
The workflow goes live with monitoring and audit logs turned on. We train your team on everyday requests and how to approve actions, so they can use the system confidently from day one.
Who benefits
- Research leads
- Interview transcripts arrive without manual handling, so analysis can start sooner.
- Media and content managers
- Episode transcripts are tracked and retrieved easily for captions, notes and archives.
- Operations and office managers
- A clear view of the transcription queue reduces follow-up emails and missed deadlines.
- Legal, HR and compliance teams
- Final transcripts are filed in restricted locations with approvals and audit records.
Security and control
- Access uses an API key with least-privilege permissions, limited to the actions your workflow needs.
- People approve any step that shares, publishes or files a transcript.
- Audit logs record each upload, status check and retrieval for later review.
- Transcripts are checked by staff before they are relied on for decisions, records or legal purposes.
- API keys can be rotated or revoked at any time if access needs to change.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can design transcription workflows that respect their state and national privacy requirements. Companies in India must consider the Digital Personal Data Protection Act, 2023, when recordings contain personal data. Businesses in the UAE and Saudi Arabia need to meet their local data protection laws, so we select a hosting region for any custom application to meet those requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the CastingWords MCP server do?
The CastingWords MCP server gives Claude a secure way to work with your transcription account. Claude can upload audio files, check the status of transcription jobs, fetch finished transcripts and manage the queue, all through plain-English requests. You keep control over which actions are permitted.
Is connecting CastingWords to Claude secure?
Security is built into the setup. Access uses an API key with least-privilege permissions, meaning Claude only gets the actions it needs. Approval steps can be added for sensitive actions, and audit logs record activity. Keys can be rotated or revoked at any time.
What can Claude do with CastingWords once connected?
Typically, Claude can upload recordings, check whether jobs are pending or complete, retrieve finalised transcripts and review the transcription queue. The exact actions available depend on how the workflow is designed and what permissions you approve.
How long does setup take?
A simple connection can be set up quickly once the workflow is agreed. Most projects also include a free audit, testing against real recordings and team training, so timelines depend on how many workflows are involved. We will give you a clear estimate after the audit.
Which plan or permissions do I need?
You need an active CastingWords account with API access, and an API key that your organisation is permitted to generate. Requirements can vary with your CastingWords arrangement, so we confirm the details with you during the free audit before any connection is made.