Skip to main content
Glama
freelancehunt-mcp

freelancehunt-mcp

Related Servers

Alternatives to freelancehunt-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      C
      maintenance
      Local MCP server for the FL.ru freelance marketplace that enables browsing projects, scoring relevance, saving proposal drafts, and dry-run proposal submission via natural language.
      17
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to search freelance projects, submit and edit bids, read and reply to employer messages, and update a freelancer profile through an unofficial integration.
      36
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables searching, filtering, and applying to IT jobs via MCP tools using a personal API key, mirroring the freehire CLI.
      45
      316 npm
      17
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables users to hunt public, ToS-safe freelance job boards, rank listings by capability match and money heat, and drive the resulting leads through Telegram cards, proposals, and follow-ups. It also tracks each lead's pipeline state from new to paid, with rituals, red-flag checks, and board-level ROI advice exposed as MCP tools.
      31
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Connects Claude-compatible clients to Freelancer.com so users can search and bid on projects, read and send messages, review bids and projects, and manage skills or specialty profiles. Supports multiple Freelancer accounts switchable per tool call.
      21
      62 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource and action, and the generic *_action tools are separated by their target resource. There is minor overlap between workspace_action and complete_contest_workspace, and a few stubbed 404 tools add noise, but the descriptions generally resolve ambiguity.

    Naming Consistency4/5

    The set is predominantly snake_case verb_noun: list_*, get_*, create_project, update_project, add_bid, send_message. The *_action batch tools are a recognizable pattern, though they are noun_noun rather than verb_noun, and complete_contest_workspace / mark_feed_read deviate slightly.

    Tool Count2/5

    With 31 tools the surface is too large for the rubric's 25+ threshold. Several tools are documented but return 404 for normal tokens, so they inflate the count without adding usable capability.

    Completeness4/5

    Core lifecycles are well covered: projects support list/find/get/create/update/actions, bids support add/list/action, workspaces have list/get/action, and threads have list/get/send/action. Missing contest creation, working profile search, and the 404 stubs keep it from a perfect score.