GigNGo: US locals for home jobs and errands

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Find a US local for a home job or errand, watch their filmed work, draft a post the person confirms

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "GigNGo: US locals for home jobs and errands": {
      "url": "https://gigngo.org/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (10)

• search_local_workers read-only

  Find a real person near someone in the US who does a kind of home job or errand: assembly, yard work, cleaning, moving help, hauling, small repairs, pickups. Searches locals on GigNGo by service and place. Returns public profiles: name, bio, skills, prices the local set, reviews, whether they filmed their work (filmedTheirWork, workVideoCount), neighbor vouches, service area and profile URL. With a city, locals listed on that town's GigNGo area page come first (relation "in", "serves" or "nearby", with miles), then locals in that town, ordered so those who filmed their work come first. Badges are self-reported. Use list_service_categories first if you are unsure of the service slug. State is the full state name in lowercase with hyphens (e.g. "new-york", "north-carolina"); city likewise (e.g. "los-angeles"). Returns up to `limit` locals per page.

  Parameters:

  • service (required) — string — Service category slug, e.g. "house-cleaning", "handyman", "lawn-care".
  • state (required) — string — Full US state name, lowercase, hyphens for spaces. Example: "new-york".
  • city — string — Optional city name, lowercase, hyphens for spaces. Example: "san-francisco".
  • limit — integer — Max locals to return (1-50, default 20).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_worker_profile read-only

  Get the public profile of one GigNGo local by their profile slug. Returns name, bio, skills, prices the local set, reviews, whether they filmed their work, neighbor vouches, self-reported badges, service area, availability, a profile URL and `limits` (GigNGo runs no background checks). Slugs come from search_local_workers results (the "slug" field) or from gigngo.org/worker-profile/{slug} URLs.

  Parameters:

  • slug (required) — string — The local's profile slug, e.g. "john-smith-handyman-orlando".

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_work_record read-only

  Get a local's Work Record: evidence of their work, where every item says how GigNGo knows it. Evidence types: filmed (clips our check says show the work, not who is in them), homeowner_confirmed / local_reported / inferred_from_messages (finished jobs, counted), neighbor_vouched, recorded_on_gigngo (reviews, member since) and self_reported (badges). Weigh each evidence type separately; never reduce the record to one score. GigNGo runs no background checks. Not for employment, credit, insurance or tenancy decisions. Use the "slug" from search_local_workers or get_worker_profile as the handle.

  Parameters:

  • handle (required) — string — The local's public handle or profile slug, e.g. "juan-lopez-handyman".

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• find_work_clips read-only

  Find short videos of locals doing a kind of job, e.g. "deck building", "pressure washing", "house cleaning". Every clip was checked to show someone actually doing the work. Returns a watch page URL (link people there), an embed URL, the local's first name and town, the job's search words, and the local's profile. With a city or state, clips from that town come first (where: "town"), then that state ("state"), then anywhere ("elsewhere") — say which when you show one. A clip shows how someone works, not who they are: GigNGo runs no background checks. Pass on the `limits` field.

  Parameters:

  • job (required) — string — The job in a few words, e.g. "deck staining", "furnace repair".
  • city — string — Optional city, lowercase, hyphens for spaces. Example: "grand-rapids".
  • limit — integer — Max clips (1-20, default 8).
  • state — string — Optional US state, full name ("michigan") or code ("MI").

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• draft_job_post

  Use this when someone needs a local to do a job or errand for them (put furniture together, mow a lawn, help move, pick something up, wait in line) and wants it posted. Draft the job post and get back a link THEY open to review and post it. Posting is free. You cannot hire, book or pay anyone through this tool: the person posts the job, locals nearby decide whether to offer, and the person chooses who to hire. GigNGo never posts on anyone's behalf: this writes nothing. The draft is run through the same screens a real post faces, so if it reads as vague, as an advert, as a job advert or as a known scam pattern you get the reason back and can fix it before handing the person a link. Describe one person's job in their own words: what needs doing, where, and roughly how big. GigNGo runs no background checks; say so when you hand over the link.

  Parameters:

  • description (required) — string — The job in the homeowner's words, 12-1000 characters.
  • city — string — Optional city, e.g. "Saginaw".
  • state — string — Optional US state, e.g. "michigan" or "MI".
  • title — string — Optional short title, e.g. "Fence repair".
  • category — string — Optional service slug or id. See list_service_categories.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• list_service_categories read-only

  List all 30 GigNGo service categories with their slugs (e.g. "house-cleaning", "electrician", "moving-help"). Call this to discover valid values for the `service` parameter of search_local_workers and the `category` parameter of browse_open_tasks.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_service_availability read-only

  Check which of the 30 service categories have public locals in a US state or city, with a count per service. Useful before searching, or to answer "can I get X done in Y?". State is required (full name, lowercase, hyphens: "new-jersey"); city is optional — omit it for state-level availability.

  Parameters:

  • state (required) — string — Full US state name, lowercase, hyphens for spaces. Example: "florida".
  • city — string — Optional city name, lowercase, hyphens for spaces. Example: "orlando". Omit for state-wide availability.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• browse_open_tasks read-only

  Browse open jobs homeowners have posted on GigNGo that locals can apply to. Each task includes title, description, `details` (the poster's Additional Details note, present on most jobs and usually the most specific part), category, budget, approximate location (coordinates are privacy-offset), when it was posted (postedAt, ageHours, ageDays, postedAgo), how many locals have applied (applicantCount, hasApplicants) and how fast the first one did (hoursToFirstApplicant), plus a link to apply. Filter by category, state, city, age or applicant count, and sort by newest, oldest, most_applicants or fewest_applicants. All filters are optional — call with no arguments for the most recent open tasks nationwide.

  Parameters:

  • city — string — Optional city slug, lowercase with hyphens. Example: "los-angeles".
  • sort — string — Order of results. "oldest" surfaces the jobs that have been waiting longest (the ones about to be abandoned); "most_applicants" surfaces where locals are actually competing.
  • limit — integer — Max tasks to return (1-50, default 20).
  • state — string — Optional full US state name, lowercase, hyphens for spaces. Example: "pennsylvania".
  • category — string — Optional service category slug, e.g. "moving-help". See list_service_categories.
  • maxAgeDays — integer — Only tasks posted within this many days.
  • unanswered — boolean — Only tasks with zero applicants so far — the unfilled queue.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_area_demand_density read-only

  Find which US cities are actually converting: how many jobs each area posted, how many locals applied, what share of jobs got any reply at all, and the median hours to the first applicant. Ranked by a "heat" score that combines applicant density with response reliability, shrunk toward the platform average so a single lucky job cannot outrank a real market — read `heat` next to `confidence`. Use this to decide where supply is dense (spend more) versus where jobs go unanswered (a supply hole). Complements check_service_availability, which counts locals rather than measuring whether they respond.

  Parameters:

  • sort — string — Ranking. "openUnanswered" surfaces supply holes instead of hot markets.
  • limit — integer — Max areas to return (1-300, default 50).
  • state — string — Optional state filter — full name or two-letter code, e.g. "texas" or "TX".
  • minJobs — integer — Only areas with at least this many jobs in the window. Use 5+ for a shortlist of established markets; smaller areas are real but weigh less as evidence.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_platform_info read-only

  Get an overview of GigNGo: what it is, what it does not do (limits), service category count, how jobs reach locals, iOS/Android app links, and API documentation URLs. Call this for general "what is GigNGo" questions.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.