YouTube Email Finder

io.github.mcp-dirPublished by GitHub account mcp-dirv0.1.0Updated Oct 24, 2026

Find the contact email of YouTube channels from the link, the @handle or the channel_id. Resolves th

The publisher's own server: Finder Jobs

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant look up the contact email of YouTube channels from a channel link, @handle or channel_id.

What you can do
  • Find contact emails for one or many YouTube channels in a single call, given a channel URL, @handle or channel_id
  • Resolve the email from the channel's contact block as well as the one in the description
  • Check platform and adapter versions, and report bugs or send feedback with recent conversation context
  • Inspect connection status, pending provider logins and the toolkit's installed MCPs and connected accounts
  • Search and describe MCPs in the platform marketplace, and log in with a browser-issued access token
When to use it
Useful when you need outreach or research contacts for YouTube creators and want the assistant to resolve channel emails directly instead of opening each channel page. Also handy for checking the platform's connection state and available tools.
Requirements
A remote MCP-over-HTTP endpoint; no local package or runtime. Works with any MCP client such as Claude, ChatGPT, Cursor or VS Code. No credentials are required for the email lookup; the authenticate tool can optionally take a bearer token for a persistent login. Network access to the hosted service.
Before you install
The server is proprietary and hosted, so channel lookups leave your machine. Data returned by the tools is sent to whichever LLM host you use, which the README names as a sub-processor outside the provider's control. Plans start at a free tier, implying paid tiers. The authenticate tool asks for an access token to be stored in the client config as an Authorization header; treat that token as a secret. The report_bug tool sends recent conversation messages for reproduction.

Installation

In SourceWeft

  1. Open YouTube Email Finder in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mcp-dir%2Fyoutube_email-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "youtube-email-finder": {
      "type": "http",
      "url": "https://api.mcp.ai/p_youtube_email"
    }
  }
}

README

YouTube Email Finder

YouTube Email Finder for Claude, ChatGPT and AI agents

Find the contact email of YouTube channels from the link, the @handle or the channel_id. Resolves the contact-block email too, not only the one in the description. Accepts many channels per call. Hosted by the platform, no credentials.

  • 📊 0 tools
  • 🔒 Read-only
  • 💬 Works with any MCP client: Claude Desktop, Cursor, VS Code, Cline, Continue
  • 🔑 Magic-link login (no password)

Versão em português · Full docs (PT-BR) · Agent skill


One-click install

Claude (Web and Desktop)

Anthropic unified MCP installation at claude.ai/customize/connectors. The same link works for Claude Web and Claude Desktop (just be logged in):

➕ Open in Claude and connect

Manual (if the deeplink does not open): claude.ai/customize/connectors → + → Add custom connector → paste Name YouTube Email Finder and URL https://api.mcp.ai/p_youtube_email.

Cursor

➕ Install YouTube Email Finder in Cursor

VS Code (Copilot Chat)

➕ Install YouTube Email Finder in VS Code

ChatGPT, Manus, OpenClaw and 40+ other clients

Works with any MCP client that speaks MCP over HTTP. The server URL is always:

https://api.mcp.ai/p_youtube_email

Per-client details: INSTALL.md.


Example prompts

Find the email for channel https://youtube.com/@mkbhdGet the emails of these channels: @mkbhd, @MrBeastWhat is the contact email of channel_id UCX6OQ3DkcsbYNE6H8uQQuVA?

0 tools available

ToolDescription

Details for each tool: docs/ferramentas.md (PT-BR)


Pricing

Plans start at a free tier. See docs/precos.md (PT-BR).


Privacy & data protection

  • Read-only, no tool changes data at the source.
  • Sub-processors: the LLM host you choose (Claude, ChatGPT, Cursor, your own agent). Full list in docs/privacidade-lgpd.md.
  • Data returned by the tools is sent to the LLM host you choose, a sub-processor outside our control. We recommend plans with training opt-out.

FAQ

Is the server open source? The server is proprietary (hosted). This repository is the public wrapper with manifests, docs and skills, all MIT.

Can I use it with my own agent (not Claude/Cursor)? Yes, any client that speaks MCP over HTTP. URL: https://api.mcp.ai/p_youtube_email.


Support


License

MIT — see LICENSE. The MCP server at api.mcp.ai/p_youtube_email is proprietary (hosted); this repo (manifests, docs, skills) is MIT.

Source: README.md at commit 0c945ae

Tools

7

youtube_email_find

Encontra o e-mail de contato de canais do YouTube. Aceita VÁRIOS canais numa chamada (`channels`): cada item pode ser o link do canal (https://youtube.com/@handle ou /channel/UC...), o @handle, ou o channel_id (UC...). Resolve também o e-mail do bloco de contato, não só o da descrição. Canal sem e-mail público volta com found=false (não é erro). Cada canal na lista conta como 1 request no plano.

Parameterschannelsrequired

show_version

Show Version

Show the current MCP platform and adapter versions.

Takes no parameters.

report_bug

Report Bug

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Parameterscontextmessagerequiredconversation

connect

Connection Status

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Takes no parameters.

toolkit_info

Toolkit Info

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Takes no parameters.

marketplace

Marketplace

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

Parameterslimitqueryactionmcp_idmessagetool_idargumentsimmediatetier_slugprompt_bodyprompt_slugprompt_tool+11 more

authenticate

Authenticate

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Parameterstoken

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Finder integrations