io.usefulapi/nocrm-io

up checked 2026-11-11T09:39:30.389Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

noCRM.io MCP by usefulapi

Publisher-provided description

Read noCRM.io leads, pipeline steps, comments and client folders; create, update and assign leads.

Summary by lookupd

Read and manage noCRM.io sales leads, pipeline steps, comments, client folders and users, including creating, updating and assigning leads.

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http nocrm-io https://nocrm-io.usefulapi.io/mcp

Codex, remote (streamable-http)

codex mcp add nocrm-io --url https://nocrm-io.usefulapi.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "nocrm-io": {
      "url": "https://nocrm-io.usefulapi.io/mcp"
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (24 tools)

Publisher-provided text

• nocrm_list_leads List or search sales leads (noCRM.io's opportunities), newest first by default, with title, pipeline step, status, amount, probability, tags, owner, next remind
• nocrm_list_unassigned_leads Leads that have no owner yet (for example web-form or API leads waiting to be handed to a salesperson). GET /leads/unassigned.
• nocrm_get_lead One lead by id: title, step, status, amount, probability, tags, owner, client folder, team, reminder, and the full description with the contact's details. GET /
• nocrm_list_lead_comments The comments (notes, logged calls/meetings/emails) on a lead, newest first by default. GET /leads/{id}/comments.
• nocrm_list_lead_history The timeline of a lead: creation, assignments, step and status changes, amount changes, comments and emails sent, with who did it and when. Filter by date range
• nocrm_get_lead_duplicates Leads that noCRM.io detects as possible duplicates of this lead (same email or key field). GET /leads/{id}/duplicates.
• nocrm_list_lead_attachments File attachments on a lead (names, ids, sizes, links). GET /leads/{id}/attachments.
• nocrm_list_follow_ups Post-sales processes (task checklists created from a template) of one lead OR of one user. Needs lead_id or user_id. Post-sales is a higher-edition feature (HTT
• nocrm_list_pipelines The sales pipelines of the account (one unless the multiple-pipelines feature is on). GET /pipelines.
• nocrm_list_steps The steps (stages) of the sales pipeline in order, with ids, positions and their pipeline. Use the ids or names when filtering leads or moving a lead. GET /step
• nocrm_list_users The users (salespeople) of the account with name, email, phone, role (admin or not) and whether they are active or deactivated. Deleted users are included, flag
• nocrm_get_user One user by id or email address. GET /users/{id}.
• nocrm_list_teams Sales teams with their members and who manages each. The Teams feature must be on in the account (HTTP 403 otherwise). GET /teams.
• nocrm_list_client_folders Client folders (accounts that group several leads), ordered by name by default. GET /clients.
• nocrm_get_client_folder One client folder by id, with its contact fields and owner. GET /clients/{id}.
• nocrm_list_activities The activity types (call, email, meeting and their outcomes) that can be set on a comment or reminder. GET /activities.
• nocrm_list_predefined_tags The account's predefined tags (admin keys only; an HTTP 401 unauthorized_non_admin means the key lacks rights). GET /predefined_tags.
• nocrm_list_fields The custom fields defined for leads or client folders. GET /fields.
• nocrm_create_lead WRITE: create a new lead. The description holds the contact's details, one 'Label: value' per line (for example 'Firstname: Ada', 'Email: ada@example.com', 'Pho
• nocrm_update_lead WRITE: change a lead: title, status (won, lost, cancelled, todo or standby), pipeline step, amount, probability, star, estimated closing date, tags (replaces th
• nocrm_assign_lead WRITE: assign a lead to a user (id or email), replacing its current owner. The owner may get a notification from noCRM.io. POST /leads/{id}/assign.
• nocrm_add_lead_comment WRITE: add a comment (an internal note) to a lead, optionally typed as an activity such as a call or meeting. It is visible to the lead's team in noCRM.io and s
• nocrm_create_client_folder WRITE: create a client folder (an account that groups leads). Not idempotent. POST /clients.
• nocrm_add_lead_to_client_folder WRITE: file a lead under a client folder. POST /leads/{id}/add_to_client.

Changes

Newest first, as lookupd saw them

• 2026-11-11: version 1.18.3 → 1.19.0

Details

• Version: 1.19.0
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 689 ms
• First indexed: 2026-11-01T10:05:28.744Z
• Last seen in registry: 2026-11-11T14:17:21.782Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/nocrm-io/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/nocrm-io.svg)](https://lookupd.com/servers/io.usefulapi/nocrm-io)

• 62092 servers
• Last crawl: 2026-11-11T17:17:22.074Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp