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
      B
      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
      23 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 11 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is noticeable overlap: raynet_full_scan largely supersedes raynet_get_structure and raynet_get_enumerations, and raynet_create_full_pipeline overlaps with raynet_create_lead_full plus raynet_convert_lead_to_bc. Descriptions help, but an agent could easily select the wrong high-level tool.

    Naming Consistency4/5

    All tools share the raynet_ prefix and mostly follow a verb_noun pattern like get_record, create_lead_full, and delete_record. However, raynet_full_scan and raynet_search break the pattern, with full_scan reading as an adjective_noun and search having no object.

    Tool Count5/5

    11 tools is within the ideal range for a CRM integration server. The count covers connection testing, schema discovery, search/retrieval, creation, conversion, and deletion without feeling bloated.

    Completeness3/5

    The server covers discovery, search, get, delete, lead creation, and lead-to-businesscase conversion, but there is no update operation at all. For a CRM integration, the inability to update existing records is a notable gap that will cause dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources