MJX CRM MCP server — connect Claude, Cursor and other AI assistants

The MJX CRM MCP server lets an AI assistant read your leads and, with a write key, add and update them when you ask in plain words. It speaks the Model Context Protocol (MCP) over Streamable HTTP and uses the same API key and rules as the REST API.

The MCP server page shows your address, the two server kinds, the tools, and copy-ready settings. Keys are made on the Integrations page.

#The address

POST https://<your-code>.pathshala.mjxtechnologies.com/mcp
Authorization: Bearer mjx_live_…
Content-Type: application/json

Copy the exact address from the MCP server page (Copy next to Address).

#Which key? "Data insights" or "Data operations"

A read-only key does not see the write tools in tools/list. If a write tool is called anyway, the answer is: "This key is read-only. The institute must make a key with "write" for …".

#Steps to connect

1. Make a key: Apps › MJX CRM › CRM settings › Advanced: API & webhooks › API keys → name it (e.g. "Claude") → pick Only read or Read and write → Make a key → copy it.
2. Copy the MCP address from Apps › MJX CRM › CRM settings › Connect AI tools (MCP).
3. Paste both into your assistant, using one of the settings below.
4. Restart the assistant and ask: "How many leads came this week?"

#Claude Desktop and Claude Code

In claude_desktop_config.json (Claude Desktop) or .mcp.json (Claude Code):

{
  "mcpServers": {
    "mjx-crm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://<your-code>.pathshala.mjxtechnologies.com/mcp",
               "--header", "Authorization: Bearer mjx_live_…"]
    }
  }
}

This uses the open-source mcp-remote bridge, so Node.js must be installed.

#Cursor

In .cursor/mcp.json:

{
  "mcpServers": {
    "mjx-crm": {
      "url": "https://<your-code>.pathshala.mjxtechnologies.com/mcp",
      "headers": { "Authorization": "Bearer mjx_live_…" }
    }
  }
}

#From your own code (Claude API MCP connector)

"mcp_servers": [{ "type": "url", "url": "https://<your-code>.pathshala.mjxtechnologies.com/mcp",
                  "name": "mjx-crm", "authorization_token": "mjx_live_…" }],
"tools": [{ "type": "mcp_toolset", "mcp_server_name": "mjx-crm" }]

Send it with the header anthropic-beta: mcp-client-2025-11-20.

#Any other MCP client

Any client that speaks Streamable HTTP and can send an Authorization header works. A raw call:

curl -X POST "https://<your-code>.pathshala.mjxtechnologies.com/mcp" \
  -H "Authorization: Bearer mjx_live_…" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

#The tools

All tools answer with JSON text built from rows in your CRM — nothing is estimated.

#search_leads (read)

Find leads. All filters are optional; newest activity first. followups_due: true lists open leads whose follow-up is today or earlier (oldest first).

Returns { leads, total, limit, offset }.

#get_lead (read)

One lead by id (required, a uuid): contact, student, class, status, tags, owner, next follow-up, extra details. Returns { lead }.

#list_tags (read)

The tags in use, with how many live leads carry each. No arguments. Returns { tags: [{ tag, count }] }.

#crm_summary (read)

Counts for a period: enquiries, talked to, joined (converted), lost, open, conversion %, by source, by person, the last 12 weeks, and follow-ups overdue / due today.

Returns totals, funnel, sources, owners, weekly, followups, response (reply times) and targets.

#create_lead (write)

Add a lead. If the phone number is already known, the existing lead is returned with duplicate: true and nothing is written. The person is not messaged.

#update_lead (write)

Change a lead's status, replace its tags, or set / clear (null) its next follow-up date (ISO 8601, e.g. 2026-11-01T10:00:00+05:30).

#add_note (write)

Add a note staff will see on the lead, signed with the key's name. Arguments: id (required), note (required, up to 1,900 characters).

#Example questions to ask

• "Which leads have not been called this week?"
• "Add a lead: Ravi Mehta, 98XXXXXX21, wants the NEET batch."
• "Tag every lead from IndiaMART as trade."
• "What did we get this month, by source?"

#Errors

Errors come back as JSON-RPC errors:

A tool that fails (for example "No lead with that id.") answers normally with isError: true and the sentence as text.

#Questions people ask