Give your AI assistant a transcription tool

The quickest route is the command line, run from the folder you work in:

claude mcp add --transport http dokitscript https://dokitscript.com/mcp \
  --header "Authorization: Bearer dks_live_YOUR_KEY"

Create .mcp.json at the root of your project, so the whole team shares the same server definition:

{
  "mcpServers": {
    "dokitscript": {
      "type": "http",
      "url": "https://dokitscript.com/mcp",
      "headers": {
        "Authorization": "Bearer dks_live_YOUR_KEY"
      }
    }
  }
}

Check it with /mcp inside a session: the server should be listed as connected, with its five tools.

Create .cursor/mcp.json in your project for a single project, or ~/.cursor/mcp.json to make the server available everywhere.

{
  "mcpServers": {
    "dokitscript": {
      "url": "https://dokitscript.com/mcp",
      "headers": {
        "Authorization": "Bearer dks_live_YOUR_KEY"
      }
    }
  }
}

Open Settings, then MCP to confirm the server shows up. If the toggle is off, switch it on there.

VS Code uses servers rather than mcpServers, and it can prompt you for the key instead of storing it in the file, which is what you want in a repository that gets committed.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "dokitscript-key",
      "description": "Dokitscript API key",
      "password": true
    }
  ],
  "servers": {
    "dokitscript": {
      "type": "http",
      "url": "https://dokitscript.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:dokitscript-key}"
      }
    }
  }
}

VS Code asks for the key the first time the server starts and remembers it after that. The tools then appear in agent mode, under the tools picker.

Claude Desktop has two doors, and neither takes a Bearer key on its own. Its Connectors panel does accept the address of a remote server, but it signs in over OAuth and offers no field for a fixed key. The configuration file, claude_desktop_config.json, starts local commands rather than calling a URL. So the route that works today is a small relay running on your machine: Claude Desktop launches it as a command, and it forwards every exchange to https://dokitscript.com/mcp over HTTPS, carrying your key in the header.

Node.js 18 or later, which is what brings npx along. Check in a terminal:

node -v

On Windows, npm also has to be installed globally, otherwise npx refuses to start. One command settles it: npm install -g npm.

Quickest way there: Settings, then Developer, then Edit Config. That opens the file, and creates it if it does not exist yet.

{
  "mcpServers": {
    "dokitscript": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://dokitscript.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer dks_live_YOUR_KEY"
      }
    }
  }
}

If the file already holds an mcpServers object, add "dokitscript" inside it instead of replacing the whole file.

The key travels through env. On Windows, Claude Desktop passes args to npx without protecting the spaces. Written inline, "Authorization: Bearer dks_live_…" is cut at the space: the relay then reads an empty header, the rest of the key is left dangling as a stray argument, and the server answers 401 while the key itself is perfectly valid. Keeping the space inside the variable puts it out of reach of whatever does the splitting. The argument names the header before the colon, and the variable carries Bearer, a space, then your key.

--transport http-only removes a guess. Our server answers POST and returns 405 to anything else, on purpose. Left to choose the transport by itself, the relay treats a 405 as its cue to fall back to a server-sent-event mode that we deliberately do not implement, a dead end that has nothing to do with your key. Naming the transport takes that branch off the table.

1. Quit the app completely, not just its window: Cmd + Q on macOS, quit from the system tray on Windows. The configuration is only read at startup.
2. Reopen it, then open the Connectors list from the control at the bottom left of the message box. dokitscript should be sitting there with its five tools.
3. Ask for something ordinary, such as list my last three transcripts. It should reach for list_transcripts on its own, without you naming the tool.

The relay stands between you and us, so the client reports a server that will not start and never shows our HTTP status. Two commands tell you which half is at fault. This one talks to us with no relay involved, and a good key answers with the five tool definitions:

curl -X POST https://dokitscript.com/mcp \
  -H "Authorization: Bearer dks_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

And this one runs the relay by hand, where its real error is printed instead of swallowed. Spaces are harmless here, because a terminal is not what was splitting them:

npx -y mcp-remote https://dokitscript.com/mcp \
  --transport http-only --debug \
  --header "Authorization: Bearer dks_live_YOUR_KEY"

The relay writes its own errors to the client log: ~/Library/Logs/Claude/mcp-server-dokitscript.log on macOS, %APPDATA%\Claude\logs\mcp-server-dokitscript.log on Windows. For the codes the server itself returns, see the table further down.

Any client that speaks MCP over HTTP and lets you set a header will work. The server takes POST requests carrying JSON-RPC 2.0 and answers as application/json. There are no sessions and no server-initiated stream, so GET and DELETE return 405 by design. To check your key by hand:

curl -X POST https://dokitscript.com/mcp \
  -H "Authorization: Bearer dks_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A working key returns the five tool definitions. Calling one looks like this:

curl -X POST https://dokitscript.com/mcp \
  -H "Authorization: Bearer dks_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"list_transcripts","arguments":{"limit":5}}}'