Skip to main content
Glama
kazan-project-manufactory

Aspro Cloud MCP

by kazan-project-manufactory
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Aspro Cloud MCP

No user-submitted related servers found.

    Related Servers

    • aspro-mcp

      bssth
      A
      license
      A
      quality
      A
      maintenance
      Enables LLMs to interact with the Aspro.Cloud REST API through self-describing tools for discovering and calling modules, entities, and methods.
      7
      20 npm
      1
      MIT

    • amoCRM MCP

      ivan000vovanov
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with amoCRM, providing access to deals, contacts, companies, notes, tasks, and custom fields via natural language.
      6 npm
      MIT

    • Kommo MCP Server

      wdavidce
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to autonomously interact with Kommo CRM, providing tools for managing pipelines, leads, contacts, and custom fields via the Kommo API v4.
      27
      1
      -

    • Pipedrive MCP Server

      ckalima
      A
      license
      B
      quality
      A
      maintenance
      Enables users to manage Pipedrive CRM data including deals, contacts, and activities directly through an AI assistant. It supports full CRUD operations, email engagement analysis, and mapping of custom field metadata for comprehensive pipeline management.
      123
      135 npm
      8
      MIT

    • Pipedrive MCP Server

      ericluciano
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the Pipedrive CRM to manage deals, contacts, organizations, and activities. It features automatic custom field synchronization and guided onboarding to ensure assistants follow specific business rules and pipelines.
      37 npm
      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

    B3.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Tools cleanly separate into leads, tasks, workflow/pipeline configuration, and users. Each tool targets a unique resource-action pair, such as list_pipelines versus list_pipeline_stages, so there is no real ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (list_*, get_*, create_*, update_*, delete_*, search_*). This makes the toolset predictable and easy to navigate.

    Tool Count4/5

    At 16 tools, the server is slightly above the ideal 3-15 range but still well-scoped. The count is justified by covering two major domains (leads and tasks) plus user lookup, with minimal redundancy.

    Completeness4/5

    Both leads and tasks have full CRUD coverage, complemented by pipeline/stage and workflow/stage listing. Minor gaps exist, such as no user listing (only search) and no CRUD for pipelines/workflows, but these are typically configuration-level and do not block core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources