MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
MCP server for Salesforce CRM — Accounts, Contacts, Opportunities, Leads, Cases.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AUTH_MODE, SALESFORCE_AUTH_FLOW, SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_INSTANCE_URL, SALESFORCE_USERNAME, SALESFORCE_PASSWORD, SALESFORCE_TOKEN, MCP_TRANSPORT, LOG_LEVELValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"salesforce": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AUTH_MODE",
"-e",
"SALESFORCE_AUTH_FLOW",
"-e",
"SALESFORCE_CLIENT_ID",
"-e",
"SALESFORCE_CLIENT_SECRET",
"-e",
"SALESFORCE_INSTANCE_URL",
"-e",
"SALESFORCE_USERNAME",
"-e",
"SALESFORCE_PASSWORD",
"-e",
"SALESFORCE_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/salesforce-mcp:v1.0.3"
],
"env": {
"AUTH_MODE": "your-value",
"SALESFORCE_AUTH_FLOW": "your-value",
"SALESFORCE_CLIENT_ID": "your-value",
"SALESFORCE_CLIENT_SECRET": "your-value",
"SALESFORCE_INSTANCE_URL": "your-value",
"SALESFORCE_USERNAME": "your-value",
"SALESFORCE_PASSWORD": "your-value",
"SALESFORCE_TOKEN": "your-value",
"MCP_TRANSPORT": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add salesforce --env AUTH_MODE=your-value --env SALESFORCE_AUTH_FLOW=your-value --env SALESFORCE_CLIENT_ID=your-value --env SALESFORCE_CLIENT_SECRET=your-value --env SALESFORCE_INSTANCE_URL=your-value --env SALESFORCE_USERNAME=your-value --env SALESFORCE_PASSWORD=your-value --env SALESFORCE_TOKEN=your-value --env MCP_TRANSPORT=your-value --env LOG_LEVEL=your-value -- docker run -i --rm -e AUTH_MODE -e SALESFORCE_AUTH_FLOW -e SALESFORCE_CLIENT_ID -e SALESFORCE_CLIENT_SECRET -e SALESFORCE_INSTANCE_URL -e SALESFORCE_USERNAME -e SALESFORCE_PASSWORD -e SALESFORCE_TOKEN -e MCP_TRANSPORT -e LOG_LEVEL ghcr.io/wyre-technology/salesforce-mcp:v1.0.3Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"salesforce": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AUTH_MODE",
"-e",
"SALESFORCE_AUTH_FLOW",
"-e",
"SALESFORCE_CLIENT_ID",
"-e",
"SALESFORCE_CLIENT_SECRET",
"-e",
"SALESFORCE_INSTANCE_URL",
"-e",
"SALESFORCE_USERNAME",
"-e",
"SALESFORCE_PASSWORD",
"-e",
"SALESFORCE_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/salesforce-mcp:v1.0.3"
],
"env": {
"AUTH_MODE": "your-value",
"SALESFORCE_AUTH_FLOW": "your-value",
"SALESFORCE_CLIENT_ID": "your-value",
"SALESFORCE_CLIENT_SECRET": "your-value",
"SALESFORCE_INSTANCE_URL": "your-value",
"SALESFORCE_USERNAME": "your-value",
"SALESFORCE_PASSWORD": "your-value",
"SALESFORCE_TOKEN": "your-value",
"MCP_TRANSPORT": "your-value",
"LOG_LEVEL": "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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"salesforce": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AUTH_MODE",
"-e",
"SALESFORCE_AUTH_FLOW",
"-e",
"SALESFORCE_CLIENT_ID",
"-e",
"SALESFORCE_CLIENT_SECRET",
"-e",
"SALESFORCE_INSTANCE_URL",
"-e",
"SALESFORCE_USERNAME",
"-e",
"SALESFORCE_PASSWORD",
"-e",
"SALESFORCE_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-technology/salesforce-mcp:v1.0.3"
],
"env": {
"AUTH_MODE": "your-value",
"SALESFORCE_AUTH_FLOW": "your-value",
"SALESFORCE_CLIENT_ID": "your-value",
"SALESFORCE_CLIENT_SECRET": "your-value",
"SALESFORCE_INSTANCE_URL": "your-value",
"SALESFORCE_USERNAME": "your-value",
"SALESFORCE_PASSWORD": "your-value",
"SALESFORCE_TOKEN": "your-value",
"MCP_TRANSPORT": "your-value",
"LOG_LEVEL": "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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SALESFORCE_AUTH_FLOW envSALESFORCE_USERNAME envMCP_TRANSPORT envLOG_LEVEL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 8, 2026
The registry name was verified with the GitHub account wyre-technology, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: AUTH_MODE, SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_INSTANCE_URL, SALESFORCE_PASSWORD, SALESFORCE_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
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
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
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.
MCP (Model Context Protocol) server for Salesforce CRM, scoped to the WYRE Gateway BYOC use case.
A focused HTTP MCP server that exposes a Salesforce org's CRM data surface to Claude (and other MCP clients) through the WYRE MCP Gateway. Built for the multi-tenant gateway pattern: credentials are injected per-request via HTTP headers, no startup secrets are baked into the container.
This package intentionally ships a narrow tool surface — six CRM data tools — and deliberately omits the Apex code-management / custom-object-creation / EXECUTE_ANONYMOUS surfaces that broader Salesforce MCP servers include. The use case is read/write access to standard CRM objects (Accounts, Contacts, Opportunities, Leads, Cases). Customers who need DX or admin tooling should use the official @salesforce/mcp package instead.
| Tool | Purpose |
|---|---|
salesforce_search_objects | Find standard + custom objects by partial name. |
salesforce_describe_object | Full schema (fields, picklists, relationships) for an object. |
salesforce_query_records | Execute SOQL with relationship traversal. |
salesforce_aggregate_query | SOQL GROUP BY / COUNT / SUM / AVG / MIN / MAX. |
salesforce_dml_records | Insert / update / delete / upsert records. |
salesforce_search_all | Cross-object SOSL search. |
:8080, exposes /mcp (JSON-RPC) + /health. Per-request credentials from X-Salesforce-* headers. This is the gateway deployment shape. HTTP refuses to start unless CONDUIT_S2S_SECRET is a real secret.CONDUIT_S2S_SECRET.Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.
| Variable | Required | Description |
|---|---|---|
SALESFORCE_CLIENT_ID / SALESFORCE_CLIENT_SECRET / SALESFORCE_INSTANCE_URL | For stdio and AUTH_MODE=env | Client Credentials flow. |
SALESFORCE_USERNAME / SALESFORCE_PASSWORD / SALESFORCE_TOKEN | For username-password | Used when SALESFORCE_AUTH_FLOW=username_password. The token is optional if the org uses IP allowlisting. |
MCP_TRANSPORT | No | http (default) or stdio. |
AUTH_MODE | No | gateway (image and Compose default) or env. Gateway mode requires the X-Salesforce-* headers on each /mcp request and never falls back to SALESFORCE_*. env uses those variables only after S2S auth succeeds. |
CONDUIT_S2S_SECRET | Yes for HTTP | Service-to-service secret. HTTP logs an error and exits non-zero when this is empty or a known placeholder (changeme, placeholder, your-s2s-secret, secret, password, test, an unresolved ${...} template, and the other stand-ins in src/s2s-verify.ts). Never commit a real value. |
MCP_ALLOW_INSECURE_DEV | No | Set to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not check X-Gateway-S2S, and listens on 127.0.0.1 only. A non-loopback MCP_HTTP_HOST is ignored and the override is logged. A known placeholder secret still refuses to start. |
MCP_HTTP_HOST | No | Bind address when a usable CONDUIT_S2S_SECRET is set. When unset, a configured secret keeps HOST (default 0.0.0.0). Without a usable secret the listener is 127.0.0.1. The container image sets 0.0.0.0. |
PORT | No | HTTP port. Defaults to 8080. |
HOST | No | Fallback bind address when MCP_HTTP_HOST is unset and a secret is configured. Defaults to 0.0.0.0. |
/health stays unauthenticated and does not read credentials.
# HTTP mode (exits unless CONDUIT_S2S_SECRET is a real secret)
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" PORT=8080 MCP_TRANSPORT=http AUTH_MODE=gateway npm start
MCP_ALLOW_INSECURE_DEV=1 MCP_TRANSPORT=http npm start
MCP_TRANSPORT=stdio \ SALESFORCE_AUTH_FLOW=client_credentials \ SALESFORCE_CLIENT_ID=... SALESFORCE_CLIENT_SECRET=... \ SALESFORCE_INSTANCE_URL=https://yourorg.my.salesforce.com \ node dist/entry.js
Every /mcp request must include a valid X-Gateway-S2S header when CONDUIT_S2S_SECRET is set. Gateway mode also requires the credential headers for the chosen flow. A request missing them returns 401 and does not fall back to SALESFORCE_* in the process environment.
| Header | Required? | Notes |
|---|---|---|
X-Gateway-S2S | Yes when the S2S secret is set | t= ,v1= . See X-Gateway-S2S signing. |
X-Salesforce-Auth-Mode | optional | client_credentials (default) or username_password. |
X-Salesforce-Client-Id | for client_credentials | Connected App consumer key. |
X-Salesforce-Client-Secret | for client_credentials | Connected App consumer secret. |
X-Salesforce-Instance-Url | for client_credentials | Customer's My Domain URL (e.g. https://acmecorp.my.salesforce.com). |
X-Salesforce-Username | for username_password | Salesforce user. |
X-Salesforce-Password | for username_password | Salesforce password. |
X-Salesforce-Token | for username_password | Security token (required unless IP allowlisted). |
Per-request authentication means the same container instance can service many customers without restart — each MCP tools/call builds a fresh jsforce.Connection from the headers on that request.
v1 is HMAC-SHA256, hex-encoded, of the ASCII string t= (the same t= prefix that starts the header), keyed with CONDUIT_S2S_SECRET. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns HTTP 401. The secret is never written to logs or the response body.
t=$(date +%s)
v1=$(printf 't=%s' "$t" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" | awk '{print $NF}') curl -sS http://127.0.0.1:8080/mcp \ -H "content-type: application/json" \ -H "accept: application/json, text/event-stream" \ -H "X-Gateway-S2S: t=${t},v1=${v1}" \ -H "X-Salesforce-Client-Id: ..." \ -H "X-Salesforce-Client-Secret: ..." \ -H "X-Salesforce-Instance-Url: https://yourorg.my.salesforce.com" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
For Client Credentials flow (the recommended path):
clientId and clientSecret.instanceUrl to the customer's My Domain URL (Setup → My Domain).npm install
npm run build
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Salesforce credentials arrive on each request as headers; they are not read from the environment.
docker build -t salesforce-mcp:dev .
docker run --rm \ -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -p 127.0.0.1:8080:8080 \ salesforce-mcp:dev curl -s http://127.0.0.1:8080/health
Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not inject SALESFORCE_*:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses SALESFORCE_*:
docker run --rm \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -e AUTH_MODE=env \ -e SALESFORCE_AUTH_FLOW=client_credentials \ -e SALESFORCE_CLIENT_ID=your-value \ -e SALESFORCE_CLIENT_SECRET=your-value \ -e SALESFORCE_INSTANCE_URL=https://yourorg.my.salesforce.com \ -p 127.0.0.1:8080:8080 \ salesforce-mcp:dev
The published image lives at ghcr.io/wyre-ai/salesforce-mcp with :latest, :sha- , and :v tags.
Apache-2.0.