txscribe

Name: txscribe
Author: txscribe-ai

by txscribe-aiversion 0.2.1i★ –iComputer or cloud

Registry nameai.txscribe/txscribe

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: TXSCRIBE_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: TXSCRIBE_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://txscribe.ai/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "txscribe": {
      "command": "npx",
      "args": [
        "-y",
        "@txscribe/mcp"
      ],
      "env": {
        "TXSCRIBE_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http txscribe https://txscribe.ai/mcp

Or run it on your computer

claude mcp add txscribe --env TXSCRIBE_API_KEY=your-value -- npx -y @txscribe/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "txscribe": {
      "command": "npx",
      "args": [
        "-y",
        "@txscribe/mcp"
      ],
      "env": {
        "TXSCRIBE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "txscribe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@txscribe/mcp"
      ],
      "env": {
        "TXSCRIBE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://txscribe.ai/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

TXSCRIBE_API_KEY secret required env
A txscribe API key (txs_live_…), made in the app under Plan and billing → Developer API.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain txscribe.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32380 servers in this category
Published to the registry more recently than 79% of the other 32380 servers in this category
Basic checks equal to or better than 100% of the other 32380 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is txscribe safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TXSCRIBE_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Dechonet MCP

by node-man

30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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

In the app, open Plan and billing → Developer API and make a key (it starts with txs_live_; you see it once).
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:

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

Claude Code:

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

Tool	What it does	Writes?
`list_transcriptions`	Your transcriptions, newest first, with paging	no
`search_transcriptions`	Which 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_link`	Create a transcription from a link (YouTube, Google Drive, Dropbox …). The recording is transcribed, never downloaded. Uses your minutes.	yes
`get_transcription`	Status and metadata of one transcription	no
`get_transcript`	The 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 instead	no
`get_summary`	The summary and its status	no
`request_summary`	Ask for a summary, or a new one, in a language and for a kind of recording	yes
`delete_transcription`	Delete 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

npm ci

npm 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)

cd mcp

npm ci && npm test npm login # an npm account that owns the @txscribe scope npm 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.

txscribe

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Dechonet MCP

README from the maker

@txscribe/mcp

Hosted: Claude and ChatGPT

Local: this package

Tools

Errors

Develop

Publish (maintainers)