noCRM.io MCP by usefulapi

io.usefulapi/nocrm-io · v1.0.0 · sales-and-crm

noCRM.io MCP by usefulapi is healthy: it completed an MCP handshake in 671 ms and exposes 24 tools.

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

Endpoint: https://nocrm-io.usefulapi.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count24
Latency671 ms
Last checked (UTC)2026-10-24T11:30:15.373Z

Health history

Checked (UTC)StatusLatencyError
2026-10-24T11:30:15.373ZHealthy671

Tools (24)

nocrm_list_leadsList or search sales leads (noCRM.io's opportunities), newest first by default, with title, pipeline step, status, amount, probability, tags, owner, next reminder and the contact details in the description. Filter by status, step (names or ids, not mixed), owner, tags, email, starred or a date range
nocrm_list_unassigned_leadsLeads that have no owner yet (for example web-form or API leads waiting to be handed to a salesperson). GET /leads/unassigned.
nocrm_get_leadOne lead by id: title, step, status, amount, probability, tags, owner, client folder, team, reminder, and the full description with the contact's details. GET /leads/{id}.
nocrm_list_lead_commentsThe comments (notes, logged calls/meetings/emails) on a lead, newest first by default. GET /leads/{id}/comments.
nocrm_list_lead_historyThe 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, action type or user. GET /leads/{id}/action_histories.
nocrm_get_lead_duplicatesLeads that noCRM.io detects as possible duplicates of this lead (same email or key field). GET /leads/{id}/duplicates.
nocrm_list_lead_attachmentsFile attachments on a lead (names, ids, sizes, links). GET /leads/{id}/attachments.
nocrm_list_follow_upsPost-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 (HTTP 403 otherwise). GET /follow_ups.
nocrm_list_pipelinesThe sales pipelines of the account (one unless the multiple-pipelines feature is on). GET /pipelines.
nocrm_list_stepsThe 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 /steps.
nocrm_list_usersThe users (salespeople) of the account with name, email, phone, role (admin or not) and whether they are active or deactivated. Deleted users are included, flagged is_disabled. GET /users.
nocrm_get_userOne user by id or email address. GET /users/{id}.
nocrm_list_teamsSales 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_foldersClient folders (accounts that group several leads), ordered by name by default. GET /clients.
nocrm_get_client_folderOne client folder by id, with its contact fields and owner. GET /clients/{id}.
nocrm_list_activitiesThe activity types (call, email, meeting and their outcomes) that can be set on a comment or reminder. GET /activities.
nocrm_list_predefined_tagsThe account's predefined tags (admin keys only; an HTTP 401 unauthorized_non_admin means the key lacks rights). GET /predefined_tags.
nocrm_list_fieldsThe custom fields defined for leads or client folders. GET /fields.
nocrm_create_leadWRITE: create a new lead. The description holds the contact's details, one 'Label: value' per line (for example 'Firstname: Ada', 'Email: ada@example.com', 'Phone: ...'); noCRM.io reads those lines. Without user_id the lead is created unassigned; a pipeline step can only be set when the lead is assi
nocrm_update_leadWRITE: change a lead: title, status (won, lost, cancelled, todo or standby), pipeline step, amount, probability, star, estimated closing date, tags (replaces the lead's tag list), or append text to the description (existing description text is never replaced). Moving to standby needs remind_date. On
nocrm_assign_leadWRITE: 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_commentWRITE: 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 sends nothing to the customer. Not idempotent. POST /leads/{id}/comments.
nocrm_create_client_folderWRITE: create a client folder (an account that groups leads). Not idempotent. POST /clients.
nocrm_add_lead_to_client_folderWRITE: file a lead under a client folder. POST /leads/{id}/add_to_client.