Skip to main content
Glama
Sign In
boondmanager-mcp-server

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
      A
      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
      MIT

    • 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.
      16 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

    The entity_action scheme plus explicit 'Plutôt que' guidance makes most tools easy to tell apart (candidates vs resources vs contacts search, per-entity tab readers vs the generic _get with `tab`). A few genuine overlaps remain: `boond_resources_timesheets` vs `boond_timesheets_search`/`_get`, `boond_resources_advantages` vs `boond_advantages_search`, and the many `*_get(tab:)` tools duplicating dedicated tab tools — but descriptions usually state which to prefer.

    Naming Consistency5/5

    Almost every tool follows `boond_<entity>_<verb>` in snake_case (search/get/create/update/delete, plus section readers like `_information`, `_technical_data`). The `boond_workflow_*` prefix groups the runbook tools predictably. No camelCase or mixed-verb chaos.

    Tool Count1/5

    238 tools is an extreme overload for any agent to navigate, with per-entity tab readers, per-entity CRUD, dictionary/config lookups, reporting, and 20+ workflow runbooks all exposed flat. The `_get(tab:)` surface alone duplicates dozens of dedicated tools, which is exactly the bloat a smaller surface would avoid.

    Completeness5/5

    Full lifecycle coverage (search/get/create/update/delete) across candidates, resources, contacts, companies, opportunities, projects, invoices, orders, purchases, timesheets, expenses, absences, contracts, positionings, documents, plus workflow runbooks, reporting, audit logs, and dictionary resolution. Almost no dead ends; helpers like `boond_find`, `boond_rights_get`, and `boond_documents_upload_slot` fill the gaps.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources