UniScribe Logo

Model Context Protocol

The UniScribe MCP Server

Give any MCP-compatible AI assistant read-only access to your transcription library. Search, read, and cite your meetings, interviews, and lectures — from Claude, Codex, or any client that speaks the protocol.

Get your API keyView setup steps
  • Streamable HTTP
  • Strictly read-only
  • No transcription minutes used

Why connect an assistant to UniScribe

Your transcripts hold answers your notes don't. The MCP server makes them queryable from the AI tools you already use.

Search one file or a whole project

Full-text search scoped to a single transcription or an entire project, so an assistant can answer from hundreds of hours of recordings at once.

Citations with deep links

Every search result includes the filename, speaker, timestamp, and original excerpt, plus a link that jumps to that exact position in the transcript.

One endpoint, many clients

Streamable HTTP with bearer-token auth means no local server to run — Claude Code, Claude Desktop, Codex CLI, and other MCP clients all connect to the same URL.

Safe to connect

All five current tools are read-only — an assistant can't modify your account, and queries don't consume transcription minutes.

Endpoint

Any MCP client that supports streamable HTTP with a bearer token can connect. Authenticate with a UniScribe API key.

MCP endpoint
https://mcp.uniscribe.co/mcp
Transport
Streamable HTTP
Authentication
Authorization: Bearer <API key>
Access
Read-only, 5 tools

Available tools

Five read-only tools cover browsing, reading, and searching your library.

list_projects

List the projects (folders) in your UniScribe workspace so the assistant can scope a question to the right one.

list_transcriptions

Browse your transcription library — recent files first, optionally filtered to a single project.

get_transcription_metadata

Fetch a transcription's details: filename, language, duration, speakers, and processing status.

get_transcript_segments

Read the transcript itself, segment by segment, with speaker labels and timestamps.

search_transcripts

Full-text search inside one transcription or across an entire project, returning matching excerpts with citations.

Connect your client

Every configuration needs a UniScribe API key — create one in Dashboard → Settings → API Keys (available on any subscription or LTD plan), then follow the guide for your client.

Claude Code

One command
  1. 1

    Run this command, replacing YOUR_API_KEY with your key:

    Terminal
    claude mcp add uniscribe --transport http https://mcp.uniscribe.co/mcp --header "Authorization: Bearer YOUR_API_KEY"

Codex CLI

TOML config
  1. 1

    Export your key in your shell profile (e.g. ~/.zshrc):

    Shell profile
    export UNISCRIBE_MCP_API_KEY="YOUR_API_KEY"
  2. 2

    Add the server to your Codex configuration:

    ~/.codex/config.toml
    [mcp_servers.uniscribe]
url = "https://mcp.uniscribe.co/mcp"
bearer_token_env_var = "UNISCRIBE_MCP_API_KEY"

Claude Desktop

Requires Node.js

Claude Desktop connects through the mcp-remote bridge, which needs Node.js installed.

  1. 1

    Open your configuration file (Settings → Developer → Edit Config), add the server, and restart Claude Desktop:

    claude_desktop_config.json
    {
  "mcpServers": {
    "uniscribe": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.uniscribe.co/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_API_KEY"
      }
    }
  }
}

If you already have other MCP servers configured, add the “uniscribe” entry inside your existing “mcpServers” object instead of replacing the file.

Other MCP clients

  1. 1

    Point the client at the endpoint above using streamable HTTP, and send your API key in the Authorization header as “Bearer YOUR_API_KEY”. Clients that only support stdio can use the mcp-remote bridge, as in the Claude Desktop config.

claude.ai web and ChatGPT connectors

Both require OAuth for remote servers, which the UniScribe MCP server doesn't support yet — API keys are the only authentication method today. OAuth support is in development, and these pages will be updated when it ships.

Example prompts to try

Once connected, talk to your transcript library the way you'd ask a colleague who was in every meeting.

“Summarize the key points from my recent interviews.”
“List my projects, then search the Customer Research project for mentions of pricing objections.”
“What did the customer say about onboarding in yesterday's call? Quote them with timestamps.”
“Compare what was said about the launch date across my last three team meetings.”

Privacy and security

The MCP server is built to give assistants the minimum access needed to answer your questions — and nothing more.

Read-only access

The current tools expose only read operations — nothing an assistant does through them can change, delete, or add data in your UniScribe account.

Queries aren't recorded

UniScribe doesn't store the content of the questions asked through MCP. Your conversations stay between you and your assistant.

Revocable keys

Access is tied to API keys you control. Delete a key in Settings at any time and that client is cut off immediately.

Learn more about how UniScribe handles your data on the Security & Privacy page and in our Privacy Policy.

Frequently Asked Questions

Client guides and API

Claude Integration

A focused walkthrough for Claude Code and Claude Desktop, with example prompts and FAQs.

Claude setup guide

ChatGPT & Codex CLI

Codex CLI works today; the ChatGPT connector arrives with OAuth support.

ChatGPT integration

REST API

Need write access? Upload files, start transcriptions, and receive webhooks with the UniScribe API.

API documentation

Connect your first assistant

Create an API key and point any MCP client at the endpoint — your entire transcript library becomes searchable from chat.

Create your API key