Skip to main content
Glama

Related Servers

Alternatives to kwork-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      B
      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
      Not graded
      quality
      Not graded
      maintenance
      An MCP server for automating Upwork workflows including job search, proposal submission, client communication, and contract management. It provides tools for client vetting, template-based proposals, and session safety with audit logging.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that connects AI coding assistants and agentic workflows to the Upwork freelance marketplace. Enables AI-powered job discovery, proposal generation, and contract management through a structured tool interface.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for searching Fiverr gigs, comparing freelancer packages, reading seller reviews, and exploring service categories. Provides structured tools for gig search, details, seller profiles, reviews, and category browsing with built-in anti-bot handling.
      5
      13
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      MCP server for the Upwork GraphQL API enabling job search, contract management, proposal drafting, and other Upwork automation tasks via natural language.
      -

    TDQS

    B3.1/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and the list/get pairs (dialogs, offers, kworks, projects) are differentiated by scope and description. Minor potential confusion remains around account_status vs. get_user_info and between several read-oriented list/get pairs, but descriptions generally resolve this.

    Naming Consistency4/5

    The set is predominantly consistent snake_case verb_noun naming: list_*, get_*, prepare_write, commit_write, reconcile_write. account_status is the main exception, and a few names like discover_projects and search_users use different verbs for similar retrieval patterns, but overall readability is high.

    Tool Count3/5

    With 22 tools, the surface is on the heavy side for a single MCP server, even accounting for Kwork's broad domain. The tools mostly earn their place, but there is room to consolidate or hide lower-level read operations.

    Completeness3/5

    Read coverage is broad across orders, dialogs, users, projects, offers, kworks, categories, and notifications, and the write lifecycle is carefully modeled. However, core lifecycle gaps remain, such as creating/editing kwork listings and broader order/payment/review operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues