Skip to main content
Glama
boostuagency

boostu-teamleader-mcp

by boostuagency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to boostu-teamleader-mcp

No user-submitted related servers found.

    Related Servers

    • suitecrm-mcp

      Anirudhx7
      A
      license
      Not graded
      quality
      B
      maintenance
      Open-source MCP gateway connecting AI agents like Claude Desktop and Claude Code to SuiteCRM. 24 CRM tools over SSE with OAuth2/OIDC auth, multi-entity support, ACL enforcement, and Prometheus/Grafana observability.
      1
      MIT

    • Bitrix24 MCP Bridge

      KarpovPartnersCom
      F
      license
      Not graded
      quality
      C
      maintenance
      A bridge between Claude (MCP) and Bitrix24 CRM/Tasks, enabling natural language interaction with leads, deals, contacts, companies, and tasks via a custom MCP server using incoming webhooks.
      -

    • pipedrive-mcp

      Dimkanarb-afk
      A
      license
      Not graded
      quality
      D
      maintenance
      Full-featured Pipedrive MCP server for Claude Desktop, enabling natural language control over deals, leads, persons, organizations, notes, activities, pipelines, and more via 34 tools and 7 prompts.
      7 npm
      MIT

    • corymbus-mcp

      laSonde
      A
      license
      A
      quality
      C
      maintenance
      Non-official MCP server for the Corymbus CRM, enabling natural language querying and modification of CRM data via MCP clients like Claude.
      13
      MIT

    • Salesmate MCP Server

      arnav-chauhan-kgpian
      A
      license
      A
      quality
      C
      maintenance
      A production-ready MCP server that exposes the Salesmate CRM to Claude Desktop, enabling search, update, and creation of contacts, deals, tasks, notes, and activities.
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.6/5.0

    Scored across 103 tools

    Disambiguation4/5

    Most tools target a distinct resource/action combination, and the many enum/list tools are clearly separated by domain. A few potential overlaps exist (events vs meetings, timer start/stop vs time_tracking_add), but descriptions generally make the intended use clear.

    Naming Consistency2/5

    Two competing conventions are used: verb_resource (list_contacts, get_invoice, create_deal) and resource_verb (contacts_add_tags, invoices_book, quotations_create), sometimes for the same resource. 'info' vs 'get' and 'list' vs 'create' are also inconsistent, and some project tool descriptions are in Dutch.

    Tool Count1/5

    With 103 tools, this is an extremely large surface for an agent to navigate, far beyond the well-scoped range. Even if each module is individually reasonable, the aggregate set is overwhelming and includes many single-purpose enum lookups that inflate the count.

    Completeness3/5

    Core workflows for contacts, deals, invoices, quotations, projects, tickets, and time tracking are mostly present. However, several resources lack obvious update/delete operations: companies have no update, tasks have no update/complete/delete, and events/meetings/calls lack update and delete tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources