Skip to main content
Glama
laSonde

corymbus-mcp

by laSonde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to corymbus-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Client Portal

      globodai-group
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server for client relationship management, enabling client tracking, notes, and search via natural language.
      MIT

    • empresa-mcp-demo

      ENtiemEN
      F
      license
      Not graded
      quality
      D
      maintenance
      Demonstration MCP server for Claude Team integration, enabling querying of sample business data (orders, clients, products) and real-time currency exchange rates through natural language.
      -

    • keycrm-mcp

      IvanKlymenko
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that lets Claude manage keyCRM catalogue, stock, orders, customers, pipelines, and more via natural language.
      3
      -
    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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct entities (accounts, contacts, opportunities, activities) with clear prefixes. The generic corymbus_list is scoped to secondary entities, but could be mistaken for a universal list alongside specific list tools. Raw_request is a clear fallback.

    Naming Consistency4/5

    The core CRUD tools follow a consistent corymbus_verb_noun pattern (list_accounts, upsert_contact). Exceptions like whoami, version, activity_types, and raw_request break the pattern but are still intuitive and not misleading.

    Tool Count5/5

    With 13 tools, the server is well-scoped for a CRM integration. Each tool serves a clear purpose, and the count is within the ideal range without unnecessary bloat.

    Completeness3/5

    Core entities have read (list) and write (upsert) coverage, but delete operations are missing entirely. Secondary entities are read-only via the generic list, and write support is absent, leaving notable gaps that must be worked around with raw_request.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources