Google Maps Leadgen

Generate B2B leads from Google Maps using a self-hosted MCP server (`google-maps`) and export to CSV or XLSX. Use when the user asks for lead generation by country/city/industry, wants phone/website/email enrichment, wants deduped lead lists, or asks to send lead files back in chat (especially Telegram file delivery).

Security Scan

The skill's purpose (Google Maps lead generation via a self-hosted MCP server) matches its code and instructions, but the manifest omits key runtime requirements (a local 'mcporter' binary and a GOOGLE_MAPS_API_KEY) and thus the package metadata is internally inconsistent and needs verification before use.

Purpose & Capability

The skill claims to generate leads via a self-hosted 'google-maps' MCP server and the provided script and SKILL.md implement that flow by calling mcporter tools (maps_search_places, maps_place_details). That purpose is coherent with the code. However, the registry metadata lists no required binaries or env vars while both the SKILL.md and the script require a local 'mcporter' binary and SKILL.md expects a GOOGLE_MAPS_API_KEY precondition — a manifest mismatch.

Instruction Scope

SKILL.md gives a focused workflow (build queries, call maps_search_places, enrich with maps_place_details, export CSV/XLSX, optionally send file via message tool). It does not instruct reading unrelated system files. It does, however, refer to a required env var (GOOGLE_MAPS_API_KEY) and reliance on mcporter configuration; the script itself invokes mcporter via subprocess rather than reading the API key directly, which is reasonable but should be documented in the manifest.

Install Mechanism

There is no install spec (instruction-only), which is lower risk in general, but the code calls an external binary ('mcporter') via subprocess and requires openpyxl for XLSX output. The manifest did not declare mcporter as a required binary nor declare dependencies. Executing subprocess calls to an undeclared local binary increases risk if users are unaware and the binary is untrusted or misconfigured.

Credentials

SKILL.md explicitly requires a server-compatible GOOGLE_MAPS_API_KEY in the environment, but the registry metadata lists no required environment variables and no primary credential. That discrepancy is important: the skill does rely on credentials (or on mcporter to hold them), and the manifest should declare this so users can judge scope and trust. No unrelated credentials are requested, but the missing declaration is the issue.

Persistence & Privilege

The skill does not request always:true, does not modify other skills' configs, and is user-invocable. It can be invoked autonomously (platform default), which is normal; nothing else in the package requests elevated or persistent privileges.

What to consider before installing

Before installing or running this skill: - Verify you or your environment administrator have a trusted mcporter binary configured for the 'google-maps' MCP server; the script will run 'mcporter' locally via subprocess. The manifest does not declare this dependency, so confirm availability and trust manually. - Confirm where the GOOGLE_MAPS_API_KEY is stored and that it is server-compatible (no browser referrer restrictions). The skill's metadata did not declare this required env var—treat this as a documentation omission and do not paste your API key into the agent or chat. - Understand that the script will create CSV/XLSX files and (per SKILL.md) may send them using the platform's message tool (e.g., Telegram). If you do not want files posted to external chats, disable or restrict the message/send capability before using. - If you plan to use XLSX output, ensure openpyxl is installed in the environment where the script runs. - Check that collecting leads at scale complies with Google Maps API terms and applicable privacy laws in target jurisdictions. - Recommended actions: ask the skill author to update the manifest to list required binaries (mcporter) and env vars (GOOGLE_MAPS_API_KEY), or only install/run this skill if you control and trust the mcporter server and local environment. Confidence note: I am moderately confident because the code and SKILL.md implement the claimed functionality, but the manifest omissions (undeclared binary and env var) are clear and could lead to unexpected behavior or risks if not clarified.

Google Maps Lead Generation (MCP)

Use this skill to run repeatable lead-gen batches from Google Maps via MCP.

Preconditions

• mcporter configured with server google-maps.
• Server key in env (GOOGLE_MAPS_API_KEY) must be server-compatible (no browser referrer restriction).
• For XLSX output, openpyxl available in venv.

Fast workflow

1. Build query set from geography + target verticals.
2. Run maps_search_places for each query.
3. Keep only in-target geography, dedupe by place_id.
4. Enrich each place with maps_place_details.
5. Export CSV or XLSX.
6. If user asks for file in Telegram, send with message tool action=send + media path.

Query strategy

Use focused terms instead of broad generic terms.

• Good: "odoo partner <city> <country>", "erp integrator <city> <country>", "logistics company <city> <country>"
• Avoid huge overlapping lists in one run; do batches.

Required output columns (V2)

• name
• address
• phone
• website
• email (empty if not discoverable)
• rating
• place_id
• google_maps_url (mobile-safe):
  • https://www.google.com/maps/search/?api=1&query=<NAME>&query_place_id=<PLACE_ID>

Cost notes

• Search calls are usually main paid SKU driver.
• Place details add enrichment cost.
• Report rough run cost estimate and mention free-tier caveat.

Reliability guardrails

• Batch enrich in small chunks (10–50) to avoid long-running timeouts.
• Add retries for transient failures.
• Never commit API keys or sensitive exports.

Delivery rules

• If user asks for CSV/XLSX file in chat: send via message tool (media path).
• If user asks specifically for XLSX formatting/edits, use xlsx workflow standards.
• Keep summary concise: count, coverage (with_phone, with_website, with_email), file path/name.