Connect Taption to VS Code

Add Taption with the setup wizard, then use your transcripts in Copilot.

Use VS Code on your computer, sign in to GitHub Copilot, and open a local project folder. Have your Taption sign-in details ready.

1. Open Add Server

Press Cmd+Shift+P on Mac or Ctrl+Shift+P on Windows/Linux. Type MCP: Add Server and select MCP: Add Server... from the list.

The Command Palette runs VS Code actions. You do not need to open a terminal.

Visual Studio Code

>MCP: Add Server

MCP: Add Server...1

MCP: Install Server from Manifest...

Visual Studio CodeEditing evolved

StartNew File...Open...Clone Git Repository...

VS CodeCopilot

2. Enter Taption’s details

Choose HTTP (HTTP or Server-Sent Events). Paste the server URL below and press Enter. Enter taption as the Server ID and press Enter again.

Use the full URL ending in /mcp-custom. No Taption API key is needed.

Visual Studio Code

1
Choose the type of MCP server to add
Command (stdio)
HTTP (HTTP or Server-Sent Events)
2
Enter Server URL
https://api.taption.com/mcp-custom
Press Enter to confirm
3
Enter Server ID
taption
Press Enter to confirm

VS CodeCopilot

3. Save the connection

Choose Global if asked, then Copilot Global. This makes Taption available across your projects.

If it does not start, run MCP: List Servers, select taption, and choose Start Server. Review the endpoint before accepting a server trust prompt.

Visual Studio Code

Add MCP Server

Select the global configuration

Copilot Global ~/.copilot/mcp-config.json1

User Configuration (deprecated)

Visual Studio CodeEditing evolved

StartNew File...Open...Clone Git Repository...

VS CodeCopilot

4. Allow access

Follow the sign-in prompt to open Taption in your browser. Sign in, check your account, review the permissions, and select ALLOW ACCESS. Return to VS Code when authorization finishes.

Allow VS Code to open your browser if asked. Sign-in may appear when you first use a tool; if already connected, continue to Enable the tools.

5. Enable the tools

Open the Command Palette again and run Chat: Open Customizations. Make sure Copilot is selected, then choose Tools. Find taption and enable its tools.

Look for list_transcripts, get_transcript, transcribe, and translate_transcript. In Local sessions, use Configure Tools in the Chat input instead.

Visual Studio Code

Agent CustomizationsCopilot

Tools

taption

translate_transcript

VS CodeCopilot

6. Try a message

Run Chat: Open Chat (Agent). Start a new chat (+), choose Copilot from the session selector, and keep Agent selected. Send the message below.

Review and approve list_transcripts if asked. Reading transcripts does not use transcription minutes.

Expand the list_transcripts tool call to confirm that Taption returned your transcripts, or an empty list.

Visual Studio Code

Chat

Build with Agent

@Taption Transcribe the attached video. It is in English; give me the output in subtitle/caption format.
@Taption Show my recent Taption transcripts.
@Taption Give me the three key tips in the video “How to bake a cake”.

Copilot

VS CodeCopilot

Manual workspace setup

Merge this sample into .vscode/mcp.json without replacing existing servers. Run MCP: List Servers → taption → Start Server, then sign in. Copilot Global uses a different format; use the wizard above.

VS Code

{
  "servers": {
    "taption": {
      "type": "http",
      "url": "https://api.taption.com/mcp-custom"
    }
  }
}

Need help connecting?

Cannot find MCP: Add Server or Copilot Global? Update VS Code and finish setting up Copilot. Your organization may need to allow custom MCP servers. For Local sessions, use the manual workspace alternative.

Connection error? Run MCP: List Servers → taption → Show Output, check the full URL, and finish sign-in. No transcripts? Check the connected Taption account; an empty library is a valid result.

Official setup guide