Skip to content
MCP server

noCRM.io MCP by usefulapi

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

Install
Runs
Remotely
Version
1.22.0
Listing updated
4 days ago

About noCRM.io MCP by usefulapi

noCRM.io MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.

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

Install

Run in a terminal

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

Add to Settings → Connectors → Add custom connector

https://nocrm-io.usefulapi.io/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "nocrm-io": {
      "url": "https://nocrm-io.usefulapi.io/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

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

Add to ~/.codeium/windsurf/mcp_config.json

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

Add to your client's MCP settings (most use this shape)

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

Tools this server provides (25)

Read directly from the server.

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_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 /leads/{id}.
nocrm_list_lead_comments
The comments (notes, logged calls/meetings/emails) on a lead, newest first by default. GET /leads/{id}/comments.
nocrm_summarize_lead_activities
Count logged activity comments by their author and activity type/outcome for 1–20 selected leads in an inclusive date range. Choose a reporting time zone (default UTC) and optionally user ids. Calls GET /activities once and GET /leads/{id}/comments once per lead, up to 21 vendor requests before retries. Parent grouping combines outcomes such as answered/unanswered under Call without double countin
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_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 (HTTP 403 otherwise). GET /follow_ups.
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 /steps.
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_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', '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_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}.
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 sends nothing to the customer. Not idempotent. POST /leads/{id}/comments.
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.

noCRM.io MCP by usefulapi FAQ

How do I add noCRM.io MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http nocrm-io https://nocrm-io.usefulapi.io/mcp