YouTube Shorts Scraper (channel Shorts, views, no login)
Pricing
from $0.80 / 1,000 result items
YouTube Shorts scraper with no API key and no login: every Short on a channel's public Shorts tab as one row with title, view count, thumbnail and channel. Optional exact views, likes and publish date per Short. Monitor mode alerts when a channel posts a new Short.
You can access the YouTube Shorts Scraper (channel Shorts, views, no login) programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
![YouTube Shorts [Only $0.45💰] Scraper avatar](https://images.apifyusercontent.com/QycCQx1quhTcnOrSBDOBxyYo4N_mTVwis9MhaMS94KQ/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vbmduOHZSRVNUa3NleVdFNnAtYWN0b3ItU1NSd2VwR0t3ekZLWWVScmstT1JvY0s0cUNoUC15dC5wbmc.webp){kind=avatar}
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,datahamster/youtube-shorts" } }}The configuration above connects to the hosted Apify MCP server with the YouTube Shorts Scraper (channel Shorts, views, no login) Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
Get a ready-to-use configuration for your MCP client with the YouTube Shorts Scraper (channel Shorts, views, no login) Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,datahamster/youtube-shorts.
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.