Connect

ChatGPT availability and custom setup

YouTube Translate is not currently listed in ChatGPT's Directory. Learn when a custom MCP connection is available and what to do without API access.

Directory availability

YouTube Translate is not currently listed in ChatGPT's Directory. Its public listing submission was rejected. There is no public directory installation to recommend, and no approval or publication date is promised.

The hosted MCP endpoint still exists. Directory review and the ability to configure a custom server are separate things. Availability of custom connections depends on your ChatGPT interface, plan, workspace, and administrator settings. A rejection does not establish permission for every other use; OpenAI's applicable policies still apply.

Start with the right kind of client

  • API-capable coding agent: give it the agent documentation. An agent with HTTP or terminal access can use REST without a directory plugin. It still needs account authorization and credits.
  • Client with custom MCP support: configure the hosted endpoint and authorize it through OAuth, if your client and workspace allow it.
  • Ordinary chat with browsing only: browsing documentation does not grant API credentials or install tools. Use the public demo for the two free examples, or obtain a transcript through a supported API/MCP client and paste the text into your chat.

Simply saying "use YouTube Translate" does not connect tools or make a browser-only conversation capable of authenticated API requests.

Optional custom MCP setup

These are manual setup instructions, not an approved Directory installation. Follow your client's current UI and applicable policies.

  1. On ChatGPT's web interface, open Plugins.

  2. If available, select the plus button, then Add custom MCP server. If that option is absent, stop: the instructions do not apply to your current account or workspace.

  3. Enter a name such as YouTube Translate, then use this server URL:

    https://api.youtubetranslate.com/mcp
    
  4. Choose OAuth. The server supports streaming HTTP, discovery, dynamic client registration, and PKCE S256. No static client secret is supplied.

  5. Review the displayed permissions and risk warning. Create the custom connection and install it if your interface requires installation.

  6. Complete sign-in on the YouTube Translate website and select Allow connection once. Account creation and OAuth approval do not add service credits.

Do not paste an account API key into the chat or an OAuth client-secret field. If using a key-based account, enter that credential only into the account website's Your user API key sign-in field.

After a connection exists

Select the connected tool in your conversation and ask for a concrete task:

Use my connected YouTube Translate tools to get a timestamped
transcript of https://www.youtube.com/watch?v=jNQXAC9IVRw.
Show me the quote and wait for approval before spending credits.

This prompt assumes the tools are already connected. It cannot install them by itself. Cached reads cost $0.002; new processing requires an approved budget. The separate public demo is free, but authenticated MCP calls for its video IDs are still metered.

Troubleshooting

  • No custom-server option: check workspace policy and current client availability. There is no universal setup-free fallback.
  • Connection expired: start a fresh connection from the client, not an old consent tab. A consent handle is one-time use.
  • Insufficient credits: the account is not funded for the requested work. Do not assume OAuth grants a free balance.
  • No tool calls after mentioning the service: confirm an actual connection exists. A model recognizing the service name is not evidence of one.

Revoke a grant from your account. For alternative clients, see Connect other clients. For API work, see Quickstart and REST API.