Skip to main content
Glama
mrchevyceleb

Crelate MCP Server

by mrchevyceleb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Crelate MCP Server

No user-submitted related servers found.

    Related Servers

    • Cronlytic MCP Server by Cronlytic

      Cronlytic MCP Serverofficial

      Cronlytic
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server that integrates with the Cronlytic API to provide seamless cron job management through LLM applications like Claude Desktop.
      1
      MIT

    • Claude Code MCP

      auchenberg
      A
      license
      B
      quality
      D
      maintenance
      An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) through the standardized MCP interface.
      8
      13 npm
      188
      MIT

    • Salesmate MCP Server

      arnav-chauhan-kgpian
      A
      license
      A
      quality
      C
      maintenance
      A production-ready MCP server that exposes the Salesmate CRM to Claude Desktop, enabling search, update, and creation of contacts, deals, tasks, notes, and activities.
      8
      MIT

    • housecall-pro-mcp

      tedmcfadden
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that wraps the Housecall Pro Public API, enabling Claude to read and write Housecall Pro data (customers, jobs, estimates, invoices, etc.) via natural language.
      23
      69 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.3/5.0

    Scored across 42 tools

    Disambiguation4/5

    Most tools have distinct purposes, e.g., get_candidate vs list_candidates. However, there is potential confusion between history tools like get_contact_history, get_job_history, and get_job_contact_history, which could overlap with get_activities. Overall, the set is largely disambiguated.

    Naming Consistency3/5

    The naming follows a consistent verb_noun pattern with get_, list_, create_, and update_. However, update_contact is the only update tool, missing updates for candidates, companies, and jobs. There are no delete tools, breaking the expected CRUD pattern. The mix of get_ and list_ is acceptable but the absence of other operations is inconsistent.

    Tool Count4/5

    With 42 tools covering candidates, companies, contacts, jobs, notes, tasks, activities, applications, placements, invoices, payments, users, tags, and workflow statuses, the count is high but justifiable for the breadth of the domain. Some tools like counts and sources could be merged, but overall it's reasonable.

    Completeness2/5

    The server is heavily read-focused with many get/list/count tools but lacks update operations for most entities (only update_contact) and has no delete tools at all. Missing operations like submitting applications, moving pipeline stages, or managing placements beyond reading leave significant gaps for a recruitment CRM lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources