noCRM.io MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 营销与社交媒体

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

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

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

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

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

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

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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, sta

• 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_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 w

• 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 n

• 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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 26 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 24 个工具描述，未发现针对 AI 的隐藏指令

与“营销与社交媒体”中的其他服务器比较i

• 星标数多于此分类中其他 3592 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 3592 个服务器的 98% 更新
• 基础检查结果等于或优于此分类中其他 3592 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{