Skip to main content
Glama

Zoho_crm

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Zoho CRM MCP Pack — wraps the Zoho CRM API v6

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
42.9% over 41 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-zoho_crm
GitHub Stars
0
Server Listing
mcp-zoho_crm

TDQS

B3.4/5.0

Scored across 36 tools

Disambiguation2/5

Only the five zoho_* tools have clearly distinct CRM actions. The other 31 tools include multiple overlapping Pipeworx research/meta tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions, entity_profile, compare_entities, validate_claim, recent_changes) that can easily cause misselection, especially since ask_pipeworx_beta is documented as currently identical to ask_pipeworx.

Naming Consistency3/5

All names use snake_case, which is consistent at the casing level. However, there is no single predictable verb_noun pattern across the set: some are prefixed by subsystem (zoho_, polymarket_, pipeworx_), others are bare verbs or noun phrases (remember, forget, validate_claim, entity_profile, recent_changes). The Zoho subset is internally consistent, but the full set mixes conventions.

Tool Count2/5

36 tools is far too many for a server named Zoho_crm, where only 5 tools actually relate to Zoho CRM. The remaining 31 tools cover unrelated domains such as prediction markets, research routing, memory, subscriptions, and npm dependency checks, making the count feel bloated and misaligned with the apparent purpose.

Completeness2/5

For a CRM server, the Zoho surface is incomplete: it supports list/get/search/create for records and modules, but has no update or delete operations, no field/metadata management, no bulk operations, and no related-list or conversion workflows. These are significant gaps that will block common CRM lifecycle tasks.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

  • Zoho CRM MCP Server

    LokiMCPUniverse
    F
    license
    B
    quality
    D
    maintenance
    Exposes Zoho CRM v6 REST API as structured tools for LLM agents via MCP, enabling CRUD operations, search, COQL queries, and more.
    11
    3
    -

  • zoho-crm-mcp

    5ivatej
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides live Zoho CRM data access via MCP tools, enabling queries on modules, records, fields, and related lists without syncing data.
    -

  • mcp-zendesk

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Zendesk MCP Pack for managing tickets, users, and organizations via OAuth.
    174 npm
    MIT

  • mcp-pipedrive

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    Wraps the Pipedrive REST API v1 to manage deals, contacts, and search across CRM entities via MCP tools.
    196 npm
    MIT
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources