Now You Can Transcribe Audio Right Inside Claude, Cursor, and Codex

Here is the news: OneStepTranscribe now works right inside your AI assistant. You can transcribe an audio or video file straight from Claude, Cursor, Codex, VS Code, or Windsurf, just by asking, and the finished transcript arrives in your inbox as PDF, Word, Markdown, and CSV. No browser tab, no upload steps, and no setup beyond your email.

We built it as an MCP server, and the first real decision behind it was not the model or the transport. It was authentication. Almost every developer tool answers this the same way: you sign up, you generate an API key, you paste it into a config file. We decided not to do that. Our MCP server has no API key and no account. You give an email address, and that is the whole of it.

That choice looks careless on the surface. It was actually the opposite, and it is worth explaining.

The pattern we refused

The default onboarding for a developer tool is a small ritual. Create an account. Confirm your email. Open a dashboard. Generate a key. Copy it into an environment variable. Later, rotate it, and revoke it if it leaks. There are good reasons this exists. A key is how a platform tells one developer from another, meters usage, and bills per seat. For a product you build your work on top of, that ritual is worth it. You do it once and forget it.

Why it is wrong for this job

The job here is not to integrate a platform. It is to transcribe one file. Someone drops a voice memo or an interview into their assistant and wants the text back. The setup for that should be close to nothing.

We refused the key for two reasons, and they carry equal weight.

The first is a promise. OneStepTranscribe has never had accounts. No login, no registration, no password to forget. That is not a missing feature, it is the product. Bolting an API key onto the MCP server would have broken that promise for exactly the audience most conditioned to accept it: developers, who paste keys into config files all day. It would have been the easy thing to ship, and the wrong one.

The second is friction measured against the size of the task. Issuing, storing, and rotating a credential is a real tax. It makes sense for something you live inside. It does not make sense for a tool you use for thirty seconds. So the email is the identity, exactly as it is on the website. If you have used the site, you already have everything you need.

What it looks like without a key

The server exposes a handful of tools, and every one of them is keyed on your email rather than a token. Your assistant checks your credit balance, prepares an upload, and starts the transcription. The audio file never travels through us: your assistant uploads it straight from your machine to storage, we transcribe it, and we email you the result as PDF, Word, Markdown, and CSV.

New accounts get a free credit automatically, and each transcription uses one credit. The equivalent of signing up is typing your email, the same step you would take on the site. There is nothing to provision and nothing to leak.

What it cost us

This is not free of trade-offs, and it would be dishonest to pretend otherwise. Without per-key identity we give up per-developer rate limiting and the tidy usage analytics a key would hand us. The endpoint is unauthenticated, which is the same posture the website has always had. We are comfortable with that because spend is still gated by credits and payment, and because the people reaching for the MCP server are the same people who use the site.

We are also not claiming this is the right call for every tool. If you sell metered access to a platform, issue keys. The point is narrower: match the authentication to the job in front of you, not to what other tools happen to do.

The takeaway

The useful lesson here has nothing to do with transcription. It is that the amount of setup you ask for should match the size of the task you are solving. For doing one small thing inside an AI assistant, the correct amount of setup is nearly zero. Meet people inside the tool they are already in, and ask for the least you can.

If you want to try it, you can add the server to Claude, Cursor, Codex, VS Code, or Windsurf from onesteptranscribe.com/mcp-server. It takes one line of config and no key.

How this was reported: this is a first-hand account of a decision made while building the OneStepTranscribe MCP server in June 2026. The mechanics described (email as identity, one credit per file, uploads that run on your own machine) are how the server works today.