Skip to main content
Glama
leomatix

raynet-mcp

by leomatix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to raynet-mcp

No user-submitted related servers found.

    Related Servers

    • CRM MCP Server

      Cerennly
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and managing a CRM database through natural language conversations with Claude Desktop.
      -

    • JobNimbus MCP Server

      drummouse
      F
      license
      B
      quality
      D
      maintenance
      Connects Claude to your JobNimbus account via API, enabling management of contacts, jobs, notes, and other CRM entities through natural language.
      19
      -

    • lawmatics-mcp

      oktopeak
      A
      license
      A
      quality
      B
      maintenance
      Connects Claude to Lawmatics legal CRM, enabling natural-language queries and management of matters, contacts, pipeline data, tasks, intake forms, and more without leaving the conversation.
      37
      38 npm
      MIT

    • MCP_Salesforce

      waaljair
      A
      license
      B
      quality
      D
      maintenance
      Enables sales, marketing, and C-suite teams to search, view, and update Salesforce records through Claude, with tools for record management, activity tracking, and global search.
      16
      MIT

    • Pipedrive MCP

      expertintegrado
      A
      license
      B
      quality
      F
      maintenance
      Enables natural language interaction with Pipedrive CRM via Claude Code, allowing users to manage deals, contacts, activities, and more through conversational commands.
      26
      11 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

    A3.6/5.0

    Scored across 12 tools

    Disambiguation3/5

    The metadata tools overlap substantially: raynet_full_scan, raynet_get_enumerations, raynet_get_structure, and raynet_get_bc_phases all retrieve structural/picklist information, differing mainly in scope. The pipeline-creation tools also overlap, since raynet_create_full_pipeline duplicates raynet_create_lead_full plus raynet_convert_lead_to_bc. Descriptions help, but an agent can still reasonably hesitate between multiple tools.

    Naming Consistency4/5

    All tools use the raynet_ prefix and snake_case, which is predictable and readable. Most follow a verb_noun pattern (get_record, update_record, delete_record, create_lead_full), with minor deviations like raynet_full_scan and raynet_search that do not follow the exact convention but remain clear.

    Tool Count5/5

    Twelve tools is well-scoped for a CRM integration that needs discovery, connection testing, CRUD, search, and pipeline creation. The set is not bloated, and each tool generally maps to a useful operation even if some overlap exists.

    Completeness3/5

    Core read, search, delete, and pipeline creation are covered, but update is restricted to lead and businessCase records only, leaving no update path for company or person records. Standalone creation of companies or persons is also absent, since creation is bundled into lead/pipeline flows. These gaps are workable for lead-centric sales workflows but incomplete for full CRM CRUD.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources