noCRM.io MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

noCRM.io MCP by usefulapi is answering right now. Last checked 14 min ago. It exposes 24 tools. Last commit 25 Oct 2026.

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

Uptime history 23 hours of history

23 hours agonow

100.0%

Uptime 24h

83 of 83 checks

Tools

read from the server

409 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

25 Oct a tool changed version4 times that day

and 3 more, back to 25 October 2026

Nothing serious here today

Today is the operative word: we check noCRM.io MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://nocrm-io.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.nocrm-io]
url = "https://nocrm-io.usefulapi.io/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "nocrm-io": {
      "type": "http",
      "url": "https://nocrm-io.usefulapi.io/mcp"
    }
  }
}

Available tools 24

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nocrm

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 sends nothing to the customer. Not idempotent. POST /leads/{id}/comments.

nocrm_add_lead_to_client_folder

WRITE: file a lead under a client folder. POST /leads/{id}/add_to_client.

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_create_client_folder

WRITE: create a client folder (an account that groups leads). Not idempotent. POST /clients.

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: [email protected]', '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 assigned. Not idempotent: calling twice creates two leads. POST /leads.

nocrm_get_client_folder

One client folder by id, with its contact fields and owner. GET /clients/{id}.

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 /leads/{id}.

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_get_user

One user by id or email address. GET /users/{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_client_folders

Client folders (accounts that group several leads), ordered by name by default. GET /clients.

nocrm_list_fields

The custom fields defined for leads or client folders. GET /fields.

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 (HTTP 403 otherwise). GET /follow_ups.

nocrm_list_lead_attachments

File attachments on a lead (names, ids, sizes, links). GET /leads/{id}/attachments.

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, action type or user. GET /leads/{id}/action_histories.

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 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. Unassigned leads are excluded unless include_unassigned is true. GET /leads.

nocrm_list_pipelines

The sales pipelines of the account (one unless the multiple-pipelines feature is on). GET /pipelines.

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_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 /steps.

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_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_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, flagged is_disabled. GET /users.

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 the lead's tag list), or append text to the description (existing description text is never replaced). Moving to standby needs remind_date. Only the fields you pass change. PUT /leads/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://nocrm-io.usefulapi.io/mcp	streamable-http	answering	235 ms	14 min ago

Alternatives to noCRM.io MCP by usefulapi

same job, measured the same way

SuiteDash MCP by usefulapi

by usefulapi

Read and update SuiteDash contacts, companies and projects; create leads and clients.

16 tools answering

Revamp CRM MCP by usefulapi

by usefulapi

Read Revamp CRM contacts, deals, notes and orders; create and update contacts, deals and notes.

19 tools answering

IDX Broker MCP by usefulapi

by usefulapi

Read IDX Broker leads, agents, listings and MLS data; create and update leads and notes.

27 tools answering

ClickUp MCP by usefulapi

by usefulapi

Read teams, spaces, lists and tasks; create, update and comment on tasks and track time.

14 tools answering

Bidsketch MCP by usefulapi

by usefulapi

Read Bidsketch clients, proposals, fees and templates; create and update clients, proposals, fees.

29 tools answering

Workiz MCP by usefulapi

by usefulapi

Manage Workiz jobs and leads: create, update, assign team members and convert leads to jobs.

19 tools answering

AddEvent MCP by usefulapi

by usefulapi

Read AddEvent calendars, events, RSVPs and subscribers; create and update calendars and events.

18 tools answering

Shipday MCP by usefulapi

by usefulapi

Read Shipday orders, carriers and delivery status; create orders and assign drivers.

14 tools answering

noCRM.io MCP by usefulapi — questions

Answers built from our own checks of this server.

What can noCRM.io MCP by usefulapi do?

It exposes 24 tools, read directly from the server on our last check. Among them: nocrm_add_lead_comment, nocrm_add_lead_to_client_folder, nocrm_assign_lead, nocrm_create_client_folder, nocrm_create_lead, nocrm_get_client_folder and 18 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is noCRM.io MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 83 of 83 checks got a reply (100.0%), average response time 409 ms. The bar chart above shows every period we have measured.

How do I connect noCRM.io MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does noCRM.io MCP by usefulapi need an API key?

No. noCRM.io MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 24 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is noCRM.io MCP by usefulapi?

It answers our handshake in 409 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is noCRM.io MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at nocrm-io.usefulapi.io, which runs on its operator's own terms.