Outscraper MCP Server
This server provides access to Outscraper's Google Maps data extraction services through two main tools:
Core Capabilities:
Google Maps Search: Find businesses and places with detailed information including names, addresses, contact details, and ratings
Google Maps Reviews: Extract customer reviews from any Google Maps place with flexible sorting and filtering options
Data Enrichment: Enhance search results with additional contact information using domain and email validation services
Key Features:
Multi-language Support: Search and extract data in different languages
Regional Filtering: Target specific countries/regions for localized results
Flexible Review Sorting: Sort by relevance, date, or rating (highest/lowest)
Time-based Filtering: Filter reviews by date using Unix timestamp cutoff
High Volume Support: Handle async processing for large requests automatically
Duplicate Removal: Option to remove duplicate search results
Use Cases:
Lead Generation: Extract business data with enriched contact information for sales and marketing
Market Research: Analyze competitors and customer sentiment through reviews and business listings
Performs Google web searches with structured results, allowing for multi-language support, regional filtering, and pagination of search results.
Extracts business data, reviews, photos, and directions from Google Maps, with capabilities for sorting, filtering, and enriching results with additional contact information.
Searches Google News with time-based filtering, pagination, and localization options to extract recent news articles.
Extracts app reviews from the Google Play Store with options for limiting results, sorting by relevance/newest/rating, and language selection.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Outscraper MCP Serverfind coffee shops in Seattle with reviews from the last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Outscraper MCP Server
A streamlined Model Context Protocol (MCP) server that provides access to Outscraper's Google Maps data extraction services. This server implements 2 essential tools for extracting Google Maps data with high reliability.
π Features
Google Maps Data Extraction
πΊοΈ Google Maps Search - Search for businesses and places with detailed information
β Google Maps Reviews - Extract customer reviews from any Google Maps place
Advanced Capabilities
Data Enrichment - Enhance results with additional contact information via enrichment parameter
Multi-language Support - Search and extract data in different languages
Regional Filtering - Target specific countries/regions for localized results
Flexible Sorting - Sort reviews by relevance, date, rating, etc.
Time-based Filtering - Filter reviews by date using cutoff parameter
High Volume Support - Handles async processing for large requests automatically
Related MCP server: OneSearch MCP Server
π¦ Installation
Installing via Smithery (Recommended)
To install the Outscraper MCP server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install outscraper-mcp --client claudeInstalling via PyPI
# Using pip
pip install outscraper-mcp
# Using uv (recommended)
uv add outscraper-mcp
# Using uvx for one-time execution
uvx outscraper-mcpManual Installation
git clone https://github.com/jayozer/outscraper-mcp
cd outscraper-mcp
# Using uv (recommended)
uv sync
# Using pip
pip install -e .π§ Configuration
Get Your API Key
Sign up at Outscraper
Get your API key from the profile page
Set Environment Variable
export OUTSCRAPER_API_KEY="your_api_key_here"Or create a .env file:
OUTSCRAPER_API_KEY=your_api_key_hereπ οΈ Client Configuration
Claude Desktop
Add to your claude_desktop_config.json:
Via Smithery (Automatic):
{
"mcpServers": {
"outscraper": {
"command": "npx",
"args": ["-y", "@smithery/cli", "run", "outscraper-mcp"],
"env": {
"OUTSCRAPER_API_KEY": "your_api_key_here"
}
}
}
}Via Local Installation:
{
"mcpServers": {
"outscraper": {
"command": "uvx",
"args": ["outscraper-mcp"],
"env": {
"OUTSCRAPER_API_KEY": "your_api_key_here"
}
}
}
}Via Manual Installation:
{
"mcpServers": {
"outscraper": {
"command": "uv",
"args": ["run", "python", "-m", "outscraper_mcp"],
"env": {
"OUTSCRAPER_API_KEY": "your_api_key_here"
}
}
}
}Cursor AI
Automatic Installation with UVX (Recommended):
{
"mcpServers": {
"outscraper": {
"command": "uvx",
"args": ["outscraper-mcp"],
"env": {
"OUTSCRAPER_API_KEY": "your_api_key_here"
}
}
}
}Manual Installation:
{
"mcpServers": {
"outscraper": {
"command": "outscraper-mcp",
"env": {
"OUTSCRAPER_API_KEY": "your_api_key_here"
}
}
}
}Note for Cursor Users: The configuration file is typically located at:
macOS:
~/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonWindows:
%APPDATA%\Cursor\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.jsonLinux:
~/.config/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
π οΈ Tools Reference
google_maps_search
Search for businesses and places on Google Maps
# Parameters:
query: str # Search query (e.g., 'restaurants brooklyn usa')
limit: int = 20 # Number of results (max: 400)
language: str = "en" # Language code
region: str = None # Country/region code (e.g., 'US', 'GB')
drop_duplicates: bool = False # Remove duplicate results
enrichment: List[str] = None # Additional services ['domains_service', 'emails_validator_service']google_maps_reviews
Extract reviews from Google Maps places
# Parameters:
query: str # Place query, place ID, or business name
reviews_limit: int = 10 # Number of reviews per place (0 for unlimited)
limit: int = 1 # Number of places to process
sort: str = "most_relevant" # Sort order: 'most_relevant', 'newest', 'highest_rating', 'lowest_rating'
language: str = "en" # Language code
region: str = None # Country/region code
cutoff: int = None # Unix timestamp for reviews after specific dateπ Running the Server
Development & Testing
# FastMCP Inspector - Web-based testing dashboard
fastmcp dev outscraper_mcp/server.py
# Then open your browser to: http://127.0.0.1:6274
# Interactive testing of Google Maps tools with real-time responsesStdio Transport (Default)
# Via PyPI installation
outscraper-mcp
# Via uv
uv run python -m outscraper_mcp
# Via manual installation
python -m outscraper_mcpHTTP Transport
from outscraper_mcp import mcp
if __name__ == "__main__":
mcp.run(transport="streamable-http", host="127.0.0.1", port=8000)π‘ Usage Examples
Example 1: Find Restaurants and Get Reviews
# 1. Search for restaurants
results = google_maps_search(
query="italian restaurants manhattan nyc",
limit=5,
language="en",
region="US"
)
# 2. Get reviews for a specific place
reviews = google_maps_reviews(
query="ChIJrc9T9fpYwokRdvjYRHT8nI4", # Place ID from search results
reviews_limit=20,
sort="newest"
)Example 2: Lead Generation with Enrichment
# Find businesses with enhanced contact information
businesses = google_maps_search(
query="digital marketing agencies chicago",
limit=20,
enrichment=["domains_service", "emails_validator_service"]
)
# Get detailed reviews for sentiment analysis
for business in businesses:
if business.get('place_id'):
reviews = google_maps_reviews(
query=business['place_id'],
reviews_limit=10,
sort="newest"
)Example 3: Market Research
# Research competitors in specific area
competitors = google_maps_search(
query="coffee shops downtown portland",
limit=50,
region="US"
)
# Analyze recent customer feedback
recent_reviews = google_maps_reviews(
query="coffee shops downtown portland",
reviews_limit=100,
sort="newest"
)π Integration with MCP Clients
This server is compatible with any MCP client, including:
VS Code with MCP extensions
Custom MCP clients
π Rate Limits & Pricing
Check Outscraper Pricing for current rates
API key usage is tracked per request
Consider implementing caching for frequently accessed data
π Troubleshooting
Common Issues
Import Error: Make sure you've installed the package correctly
pip install --upgrade outscraper-mcpAPI Key Error: Verify your API key is set correctly
echo $OUTSCRAPER_API_KEYNo Results: Check if your query parameters are valid
Rate Limits: Implement delays between requests if needed
Enable Debug Logging
import logging
logging.basicConfig(level=logging.DEBUG)π€ Contributing
Fork the repository
Create a feature branch
Make your changes
Add tests
Submit a pull request
π License
Experimental Software License - see LICENSE file for details.
Notice: This software is experimental and free to use for all purposes. Created by Jay Ozer.
π Links
Built with Blu Goldens
Available Tools
2 toolsgoogle_maps_reviewsB
Extract reviews from Google Maps places using Outscraper
Args:
query: Place query, place ID, or business name (e.g., 'ChIJrc9T9fpYwokRdvjYRHT8nI4', 'Memphis Seoul brooklyn usa')
reviews_limit: Number of reviews to extract per place (default: 10, 0 for unlimited)
limit: Number of places to process (default: 1)
sort: Sort order for reviews ('most_relevant', 'newest', 'highest_rating', 'lowest_rating')
language: Language code (default: 'en')
region: Country/region code (e.g., 'US', 'GB', 'DE')
cutoff: Unix timestamp to get only reviews after this date
Returns:
Formatted reviews data with place information and individual reviews
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| reviews_limit | No | ||
| limit | No | ||
| sort | No | most_relevant | |
| language | No | en | |
| region | No | ||
| cutoff | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions 'Extract reviews' and 'Returns: Formatted reviews data', which implies a read-only operation, but doesn't disclose critical behavioral traits like rate limits, authentication needs, data freshness, or potential costs. For a tool with 7 parameters and no annotations, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with clear sections (purpose, Args, Returns) and uses bullet-like formatting. It's appropriately sized for a 7-parameter tool, with each sentence adding value. Minor improvements could include more front-loaded context, but overall it's efficient and readable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (7 parameters, no annotations, no output schema), the description is partially complete. It excels in parameter semantics but lacks behavioral context (e.g., rate limits, errors) and output details beyond 'Formatted reviews data'. For a data extraction tool, more output structure guidance would help, but the parameter coverage raises it above minimal viability.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description provides detailed parameter semantics in the 'Args' section, explaining each parameter's purpose with examples (e.g., 'query: Place query, place ID, or business name'). With 0% schema description coverage, this fully compensates by adding meaning beyond the bare schema. However, it doesn't cover all nuances (e.g., exact format for 'cutoff' as Unix timestamp).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Extract reviews from Google Maps places using Outscraper.' It specifies the verb ('extract'), resource ('reviews from Google Maps places'), and method ('using Outscraper'). However, it doesn't explicitly differentiate from its sibling 'google_maps_search', which likely searches for places rather than extracting reviews.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It mentions the sibling tool 'google_maps_search' in the context signals, but the description itself offers no explicit when/when-not instructions or comparisons. Usage is implied through the purpose statement but lacks actionable guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
google_maps_searchA
Search for businesses and places on Google Maps using Outscraper
Args:
query: Search query (e.g., 'restaurants brooklyn usa', 'hotels paris france')
limit: Number of results to return (default: 20, max: 400)
language: Language code (default: 'en')
region: Country/region code (e.g., 'US', 'GB', 'DE')
drop_duplicates: Remove duplicate results (default: False)
enrichment: Additional services to run (e.g., ['domains_service', 'emails_validator_service'])
Returns:
Formatted search results with business information
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| limit | No | ||
| language | No | en | |
| region | No | ||
| drop_duplicates | No | ||
| enrichment | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool uses Outscraper and returns formatted results, but lacks critical details like rate limits, authentication requirements, pagination behavior, error handling, or whether it's a read-only operation. For a search tool with 6 parameters, this is insufficient behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with clear sections (Args, Returns), uses bullet-like formatting for parameters, and every sentence adds value. It's appropriately sized for a tool with 6 parameters and no annotations, with no redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (6 parameters, no annotations, no output schema), the description covers purpose and parameters well but has significant gaps. It lacks behavioral context (rate limits, auth), doesn't explain the return format beyond 'formatted search results', and provides no error handling information. The parameter coverage is excellent, but other aspects are incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description fully compensates by providing clear explanations for all 6 parameters. Each parameter gets practical examples (e.g., query examples), default values, constraints (max limit), and usage context (e.g., what enrichment services do). This adds substantial meaning beyond the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches for businesses and places on Google Maps using Outscraper, providing a specific verb ('search') and resource ('businesses and places on Google Maps'). It distinguishes from the sibling tool google_maps_reviews by focusing on search rather than reviews. However, it doesn't explicitly contrast with the sibling beyond the different function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage through the purpose statement and parameter explanations, suggesting it's for finding businesses/places. However, it lacks explicit guidance on when to use this tool versus alternatives (like the sibling google_maps_reviews) or any prerequisites. The context is clear but not comprehensive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
The two tools have clearly distinct purposes: google_maps_reviews extracts reviews from specific places, while google_maps_search finds businesses and places based on queries. There is no overlap in functionality - one is for retrieving existing reviews, the other is for discovering places.
Both tools follow the exact same naming pattern: google_maps_ followed by a descriptive action (reviews, search). The naming is perfectly consistent and immediately communicates what each tool does within the Google Maps/Outscraper domain.
With only 2 tools, this server feels significantly under-scoped for what appears to be a Google Maps data extraction service. While the two tools cover basic search and review extraction, there are likely many other Google Maps operations that would be valuable (business details, photos, directions, etc.).
For a Google Maps data extraction server, the surface is severely incomplete. While search and review extraction are useful starting points, there's no coverage for getting detailed business information, extracting photos, retrieving directions, accessing opening hours, or other common Google Maps operations. Agents will hit dead ends trying to perform comprehensive Google Maps tasks.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.
Outscraper MCP business discovery, Maps intelligence, enrichment, reviews, and contact data.
The Google Maps MCP server is a fully-managed server provided by the Maps Grounding Lite API that connects AI applications to Google Maps Platform services. It provides three main tools for building LLM applications: searching for places, looking up weather information, and computing routes with details like distance and travel time. The server acts as a proxy that translates Google Maps data into a format that AI applications can understand, enabling agents to accurately answer real-world location and travel queries.
Live Google Maps business search, review, and photo data for AI agents over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows LLMs to interact with web content through standardized tools, currently supporting web scraping functionality.1MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including SearXNG, Firecrawl, and Tavily.4190139MIT
- AlicenseBqualityAmaintenanceA Model Context Protocol server that provides Google Maps API integration, allowing users to search locations, get place details, geocode addresses, calculate distances, obtain directions, and retrieve elevation data through LLM processing capabilities.71,992428MIT

Outscraper MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceProvides access to Outscraper's data extraction services for business intelligence, location data, and reviews across platforms like Google Maps, Amazon, and Yelp. It enables AI assistants to perform comprehensive web scraping tasks including contact information retrieval and geolocation services.6MIT
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jayozer/outscraper-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server