Skip to main content
Glama
botdigit-official

Botdigit MCP

by botdigit-official
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Botdigit MCP

No user-submitted related servers found.

    Related Servers

    • Workix MCP

      facetoplace
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search a shared catalog of projects, roles, orders, participants, and mentors, create and update listings or profiles, draft proposals, and search and apply across external freelance and job platforms while keeping platform credentials local.
      13
      -

    • NiPlex MCP Server

      Aj-Niplex
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with production-ready integrations for GitHub repository management, sandboxed code execution, SFTP file operations, web search and scraping, YouTube, Google Workspace, Notion, and more.
      -

    • upwork-mcp

      furkankoykiran
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI agents to Upwork's GraphQL API, enabling job discovery, proposal management, profile tracking, and analytics.
      9 npm
      2
      MIT

    • @txn-dev/mcp-server

      polyxmedia
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants such as Claude, Cursor, and Windsurf to create and fund agent wallets, check balances, and move money idempotently between wallets. It also lets them find and hire people by skill, rate, and rating through posted jobs with escrowed budgets, deliverables, payment release, and disputes.
      13
      21 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool targets a fairly distinct resource and action (projects, proposal drafts, bids, messages, contracts, milestones). The main overlap risk is between proposal drafts, bids, and projects, but the descriptions clarify that projects are marketplace listings, drafts are staged, and bids are submitted. Minor boundary blur between a staged proposal draft and a submitted bid.

    Naming Consistency5/5

    Every tool uses the botdigit_ prefix followed by a clean verb_noun pattern (list_projects, get_project, stage_proposal_draft, approve_proposal_draft, get_thread, etc.). The 'stage' action verb is applied uniformly across drafts. No mixing of conventions.

    Tool Count5/5

    13 tools sit comfortably in the well-scoped 3-15 range. Each tool maps to a distinct operation across the browse/stage/approve/list workflow, with no obviously redundant tools.

    Completeness3/5

    Core flows (browse projects, stage/approve proposals, read messages, view contracts/milestones) are covered, but the lifecycle is asymmetric: proposals have both stage and approve tools, while messages and delivery drafts can only be staged with no matching approve tool. There is also no get for proposal drafts and no way to reject/decline a draft or bid, creating potential dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources