txscribe

ai.txscribePublished by txscribe.aiOfficial publisherv0.2.1Updated Oct 29, 2026

Transcribe a link, then read the transcript and summary from your txscribe account.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowMedia & Design

Overview

AI-generated overview

Connects an assistant to a txscribe account to transcribe links and read back transcripts, summaries and search matches.

What you can do
  • Create a transcription from a link such as YouTube, Google Drive or Dropbox, using your account minutes
  • List your transcriptions newest first with paging, and search finished recordings for a word or phrase with start times
  • Check status and metadata of a single transcription
  • Read a finished transcript as json, txt, srt or vtt, optionally only the paragraphs around a moment, or fetch the summary
  • Request a summary or a new one in a chosen language and for a kind of recording
  • Delete a transcription and everything made from it
When to use it
Useful when you want an assistant to turn a shared video or audio link into a transcript or summary inside a chat, or to find where something was said in recordings already in your txscribe account. File uploads are not supported, so use the app or API for local files.
Requirements
Either the hosted endpoint with OAuth sign-in (or an API key header), or the local npm package run with npx, which needs Node.js and the TXSCRIBE_API_KEY environment variable. A txscribe account with available minutes is required; TXSCRIBE_API_BASE can point at another deployment.
Before you install
The API key (TXSCRIBE_API_KEY) is a live credential shown once and does not expire on its own; revoke it in the app if exposed. Transcribing a link spends your account minutes, and request_summary and delete_transcription change your account; deletion is permanent and cannot be undone. Links you submit are sent to txscribe for processing.

Installation

In SourceWeft

  1. Open txscribe in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.txscribe%2Ftxscribe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "txscribe": {
      "type": "http",
      "url": "https://txscribe.ai/mcp"
    }
  }
}

README

@txscribe/mcp

An MCP server for the txscribe developer API. It lets an AI assistant transcribe a link with your txscribe account and read the transcript and the summary back, through the same API documented at https://txscribe.ai/developers.

There are two ways to connect, with the same eight tools:

  • Hosted — https://txscribe.ai/mcp (Streamable HTTP). Claude and ChatGPT connect to it as a custom connector and sign you in to txscribe with OAuth; nothing to install. Clients that take a header can send an API key instead.
  • Local — this package, run as a command (npx -y @txscribe/mcp) by Claude Desktop, Claude Code, Cursor and other clients that start MCP servers themselves, with your API key in its environment.

Both are thin wrappers: every tool is one call to the developer API as you. What a tool may do, and the minutes it uses, is exactly what your account may do in the app. Nothing is cached or stored on your machine.

Hosted: Claude and ChatGPT

  • Claude (claude.ai, the desktop app): Settings → Connectors → Add custom connector, URL https://txscribe.ai/mcp. Claude opens txscribe; sign in and choose Allow.
  • ChatGPT (with developer mode on): add a connector with the URL https://txscribe.ai/mcp and OAuth as its authentication, then allow it on the txscribe page that opens.
  • Claude Code: claude mcp add --transport http txscribe https://txscribe.ai/mcp (it signs in with OAuth), or with a key: claude mcp add --transport http txscribe https://txscribe.ai/mcp --header "Authorization: Bearer txs_live_…".
  • Cursor and others that take a URL and headers: the URL above with the header Authorization: Bearer txs_live_….

A connection made with Allow is an API key the app holds for you. It is listed under Plan and billing → Developer API, where Revoke disconnects that app. It does not expire on its own.

Local: this package

  1. In the app, open Plan and billing → Developer API and make a key (it starts with txs_live_; you see it once).
  2. Add the server to your client with the key in its environment.

Claude Desktop (claude_desktop_config.json) or any client that takes a command:

json
{  "mcpServers": {    "txscribe": {      "command": "npx",      "args": ["-y", "@txscribe/mcp"],      "env": { "TXSCRIBE_API_KEY": "txs_live_…" }    }  }}

Claude Code:

bash
claude mcp add txscribe --env TXSCRIBE_API_KEY=txs_live_… -- npx -y @txscribe/mcp

TXSCRIBE_API_BASE points the server at another deployment (default https://txscribe.ai/api/v1).

Tools

ToolWhat it doesWrites?
list_transcriptionsYour transcriptions, newest first, with pagingno
search_transcriptionsWhich recordings said a word or phrase, and when: up to five matches each, with the second they start at. Reads the finished ones among your newest 500 recordings; searches what was said, not titles.no
transcribe_linkCreate a transcription from a link (YouTube, Google Drive, Dropbox …). The recording is transcribed, never downloaded. Uses your minutes.yes
get_transcriptionStatus and metadata of one transcriptionno
get_transcriptThe finished transcript as json (segments, word timings, speakers), txt, srt or vtt; from and to (seconds) for only the paragraphs around a moment, summaryOnly for the summary insteadno
get_summaryThe summary and its statusno
request_summaryAsk for a summary, or a new one, in a language and for a kind of recordingyes
delete_transcriptionDelete a transcription and everything made from it. Cannot be undone.yes, destructive

Five tools only read; three change your account. Uploading a file is not a tool: the API's upload is a signed PUT of the whole file, which an assistant cannot make from a chat. Use the app, or the API directly, for files.

A typical exchange: "Transcribe this talk and give me the three claims to check" → transcribe_link → get_transcription until status is done → get_transcript (txt) → the assistant reads it; request_summary + get_summary for the summary txscribe makes.

Finding something in recordings you already have: "What did we agree about the budget?" → search_transcriptions ("budget") → get_transcript with from/to around the matches it returned, instead of whole transcripts.

Errors

API refusals come back as tool errors with the API's own code (invalid_api_key, quota_exceeded, not_ready, unsupported_link …), the HTTP status, the request id to quote to support and, on 429, the Retry-After seconds. Neither server retries anything itself.

Develop

bash
npm cinpm test

The tests run the server over an in-memory transport against a fake fetch; nothing reaches the network. The hosted server lives in the web app (web/src/lib/mcp/), and its tests check that its tool list matches this one.

Publish (maintainers)

bash
cd mcpnpm ci && npm testnpm login                      # an npm account that owns the @txscribe scopenpm publish                    # publishConfig makes it public; prepublishOnly runs the tests

server.json is the entry for the MCP Registry (registry.modelcontextprotocol.io); its name matches mcpName in package.json, which is how the registry checks the npm package is ours. Publish it after the npm package is up and the hosted endpoint is switched on, with mcp-publisher and DNS proof of txscribe.ai.

Source: README.md at commit 156d8f4

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.2.1LatestOct 29, 2026
  2. v0.2.0Oct 25, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts