AutomationNation data tools (via Apify) vs MCP Domain To Linkedin Url Resolver
A side-by-side look at the AutomationNation data tools (via Apify) and MCP Domain To Linkedin Url Resolver MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AutomationNation data tools (via Apify)Search & Data Extraction · Local subprocess (stdio)Google Shopping, Flights, Hotels, News, Images, Ads, Jobs, Trends, YouTube transcripts, leads.52GoodAuth: not declaredVerdict: choose AutomationNation data tools (via Apify) for search & data extraction work as a local process; choose MCP Domain To Linkedin Url Resolver for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose AutomationNation data tools (via Apify) when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
APIFY_TOKEN. - You want tools like
search_flights, search_hotels, search_google.
Choose MCP Domain To Linkedin Url Resolver when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
APIFY_TOKEN. - You want tools like
resolve_linkedin_url.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A AutomationNation data tools (via Apify) | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 52/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | APIFY_TOKEN | APIFY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 19 | 1 |
| Full listing | View AutomationNation data tools (via Apify) | View MCP Domain To Linkedin Url Resolver |
Tools & capabilities
AutomationNation data tools (via Apify) tools 19
search_flightsSearch Google Flights for one route and date.search_hotelsSearch Google Hotels for a city, neighbourhood or landmark.search_googleSearch Google and get the web results in Google's order: title, URL, site and snippet for each.search_google_shoppingSearch Google Shopping for a product in any country.get_youtube_transcriptsGet the transcript (captions) of YouTube videos, with title, channel, duration, caption language and word count, and optional timestamps.search_google_newsSearch Google News for a topic, company or person.search_google_imagesSearch Google Images.search_google_videosSearch Google's video results across YouTube, TikTok, Vimeo, news sites and more.search_jobsSearch Google Jobs, which aggregates listings from LinkedIn, Indeed, Glassdoor, company career sites and more, in 26 countries.get_google_trendsGoogle Trends for up to 5 keywords: interest over time (0–100), average, latest and peak interest, trend direction and change, top regions, and top and rising related searches with "Breakout" flags.get_trending_searchesWhat's trending on Google right now in a country, like trends.google.com/trending: each trending search with its search volume, increase, start time, whether it is still active, related searches and optional news articles.find_local_businessesFind local businesses on Google Maps in any country, as sales leads.- +7 more on the listing page
MCP Domain To Linkedin Url Resolver tools 1
resolve_linkedin_urlResolve a company domain or name to its LinkedIn company URL. Returns the LinkedIn URL with a confidence score, plus firmographics such as employee count, industry, and headquarters, and social links, as a flat, Clay-ready JSON row. Provide at least one of company_domain or company_name. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AutomationNation data tools (via Apify)
{
"mcpServers": {
"automationnation-data-tools-via-apify": {
"command": "npx",
"args": [
"-y",
"github:retracn/automationnation-mcp"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
MCP Domain To Linkedin Url Resolver
{
"mcpServers": {
"mambalabsdev-mcp-domain-to-linkedin-url-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
Frequently asked questions
AutomationNation data tools (via Apify) is categorized under Search & Data Extraction and uses a local stdio subprocess. MCP Domain To Linkedin Url Resolver belongs to Search & Data Extraction and uses a local stdio subprocess. Pick AutomationNation data tools (via Apify) for search & data extraction work and MCP Domain To Linkedin Url Resolver for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AutomationNation data tools (via Apify) is bring-your-own-key: usage is billed by the API provider you supply a key for. MCP Domain To Linkedin Url Resolver is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add automationnation-data-tools-via-apify and mambalabsdev-mcp-domain-to-linkedin-url-resolver as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AutomationNation data tools (via Apify) has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MCP Domain To Linkedin Url Resolver has 61/100 (Good) with 3 views, 0 installs and 2 GitHub stars.