Skip to main content
Glama
silamir

boondmanager-mcp-server

by silamir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to boondmanager-mcp-server

No user-submitted related servers found.

    Related Servers

    • BoondManager MCP Server

      inakirealise
      F
      license
      C
      quality
      D
      maintenance
      An MCP server integrating with the BoondManager API to enable AI assistants to search, retrieve, create, and update records across 94 tools in 8 business domains.
      95
      -

    • Neo MCP

      heydryft
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server with 206+ tools across 16 integrations that gives Claude access to real accounts (LinkedIn, Twitter, Slack, Gmail, WhatsApp, etc.) by extracting auth tokens straight from your browser, no API keys or OAuth needed.
      10 npm
      3
      MIT

    • odoo-mcp-simple

      fsmw
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server to connect Claude with Odoo 18, enabling CRUD operations on Odoo models via natural language.
      2
      -

    • Follow Up Boss Connector

      thehillisrockin
      F
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that connects a Follow Up Boss CRM account to Claude, enabling CRM operations through natural language via 25 curated tools and a raw API tool.
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.1/5.0

    Scored across 238 tools

    Disambiguation4/5

    Each tool carries a highly explicit 'Quand' / 'Plutôt que' section naming the exact sibling tool to use instead, which is exceptional guidance for telling tools apart. However, with 238 tools there is real residual ambiguity between overlapping surfaces: the generic `*_get` with a `tab` parameter vs dedicated tab tools (e.g. `boond_candidates_get` vs `boond_candidates_information`) and the workflow runbooks vs their identical prompts.

    Naming Consistency5/5

    Tools follow a rigorous `boond_<entity>_<action>` snake_case convention (search/get/create/update/delete) across every domain, with tab and default variants using the same scheme. The only minor deviations are the French-named `boond_workflow_*` group and a stray `groupments`, which don't break the pattern.

    Tool Count1/5

    238 tools is an extreme mismatch for the surface, driven by mechanically generated CRUD (create/get/update/delete/search) replicated across ~30 entities plus dozens of tab, default, and workflow tools. Many workflow runbooks merely re-expose prompts already available, adding count without adding capability.

    Completeness5/5

    The surface provides full lifecycle coverage (search/get/create/update/delete) for every entity, plus section tabs, write-side defaults for CRA/expenses/absences, reporting aggregates, dictionary resolution, rights checks, document upload, and multi-step runbooks. There are essentially no dead ends in the domain.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources