Pipeline CRM MCP by usefulapi

安装

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

通过 4/4 项检查 · 你的提问会经过开发者的服务器（pipeline-crm.usefulapi.io） · ✓ 命令已检查 2026年11月13日

claude mcp add --transport http --scope user pipeline-crm https://pipeline-crm.usefulapi.io/mcp

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

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

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

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

• pipelinecrm_get_profile

  The Pipeline CRM user this credential acts as: id, name and whether they are an account admin. The user's api_key is never returned. GET /profile.

• pipelinecrm_list_users

  List the users of the Pipeline CRM account (id, name, email, team, admin flag). Use the ids as owners of deals, people and companies. api_key values are never returned. GET /users.

• pipelinecrm_get_user

  One user of the account by id. The user's api_key is never returned. GET /users/{id}.

• pipelinecrm_list_deals

  List or search deals with stage, owner, company, primary contact, value, probability and expected close date. Filter by name, stage, pipeline, status, owner, company, contact, archived flag, value range and created, expected-close, closed or modified dates. Money values come back

• pipelinecrm_get_deal

  One deal by id with owner, company, people, stage, status, loss/won reasons, tags, custom fields and the next task. GET /deals/{id}.

• pipelinecrm_deal_totals_by_stage

  Count and total value of the deals visible to the user in every deal stage: the pipeline summary. GET /deals/totals_by_stage.

• pipelinecrm_list_deal_notes

  List the notes (activities) logged on one deal, with author, category and content. GET /deals/{id}/notes.

• pipelinecrm_create_deal

  WRITE: create a deal. Give the owner (user id), stage id, value, expected close date and company or primary contact when known; a new company is created from company_name if no company_id is given. No email is sent to the owner. POST /deals.

• pipelinecrm_update_deal

  WRITE: change fields of a deal; only the fields you pass change. Move it to another stage with stage_id. Setting probability to 100 or 0 closes the deal as won or lost; give won/loss reason ids when you do. Archive with archived: true. No email is sent to a new owner. PUT /deals/

• pipelinecrm_list_people

  List or search people (leads and contacts) with email, phones, position, company, owner, lead status and tags. Use search for a quick match on name, email or company name, or filter precisely. GET /people.

• pipelinecrm_get_person

  One person (lead or contact) by id with all contact details, company, owner, tags and custom fields. GET /people/{id}.

• pipelinecrm_list_person_deals

  List the deals one person is associated with. GET /people/{id}/deals.

• pipelinecrm_list_person_notes

  List the notes (activities) logged on one person. GET /people/{id}/notes.

• pipelinecrm_create_person

  WRITE: create a lead or contact. Pass at least a first or last name or an email. No email is sent to the owner. POST /people.

• pipelinecrm_update_person

  WRITE: change fields of a person; only the fields you pass change. Pass type Contact to convert a lead. PUT /people/{id}.

• pipelinecrm_list_companies

  List or search companies with address, website, phones, owner, tags and pipeline totals. GET /companies.

• pipelinecrm_get_company

  One company by id with address, phones, website, owner, tags and custom fields. GET /companies/{id}.

• pipelinecrm_list_company_people

  List the people (leads and contacts) who work at one company. GET /companies/{id}/people.

• pipelinecrm_create_company

  WRITE: create a company. POST /companies.

• pipelinecrm_update_company

  WRITE: change fields of a company; only the fields you pass change. PUT /companies/{id}.

• pipelinecrm_list_notes

  List notes (called activities in the Pipeline CRM app) attached to a deal, person or company. Pass at least one of deal_id, person_id, company_id. Filter by text, category, author and created date. GET /notes.

• pipelinecrm_get_note

  One note (activity) by id with its content, author, category, associations and comments. GET /notes/{id}.

• pipelinecrm_add_note

  WRITE: log a note (activity) on a deal, person or company. Pass at least one of deal_id, person_id, company_id. POST /notes.

• pipelinecrm_list_calendar_entries

  List calendar entries: tasks (a due date) and events (a start and end time) tied to deals, people or companies. Filter by kind, owner, a date range, and completed, incomplete or late. GET /calendar_entries.

• pipelinecrm_get_calendar_entry

  One calendar entry (task or event) by id. GET /calendar_entries/{id}.

• pipelinecrm_create_calendar_entry

  WRITE: create a task (CalendarTask, optional due date) or an event (CalendarEvent, start_time and end_time required), optionally tied to a deal, person or company. POST /calendar_entries.

• pipelinecrm_update_calendar_entry

  WRITE: change a task or event; only the fields you pass change. Pass complete: true to mark a task done. PUT /calendar_entries/{id}.

• pipelinecrm_list_deal_stages

  List the deal stages with id, name, default win probability and the pipeline each belongs to. Use the ids to filter or move deals. GET /admin/deal_stages.

• pipelinecrm_list_deal_pipelines

  List the deal pipelines (each has its own stages) with id, name and which one is the default. GET /admin/deal_pipelines.

• pipelinecrm_list_lookup

  List one set of account lookup values to get ids for filters and writes. kind: deal_statuses, deal_loss_reasons, deal_won_reasons, deal_tags, lead_statuses, lead_sources, contact_tags, company_tags, note_categories, event_categories, task_priorities, task_statuses, teams. GET /ad

基础检查i

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

• ✓ 通过

  作者与仓库一致

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

• ✓ 通过

  仍在维护

  代码最后更新于昨天

• – 不适用

  有许可证

  不适用：由 usefulapi.io 的所有者自己运行的云端服务器，你不会运行仓库里的代码

• ✓ 通过

  端点有响应

  在 23 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

我们检查什么 → · JSON

用户评价

还没有评价

登录后写评价

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

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

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

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面，再按星标排序。

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

Relaticle

Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.

作者：relaticle·正在增长·★ 1844·前天更新

在云端运行✓ 服务方 · relaticle.com

接入方法

ChatbotX

Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.

作者：ChatbotXIO·正在增长·★ 1120 整个仓库的星标·9天前更新

在云端运行✓ 服务方 · chatbotx.io

接入方法

X (Twitter) MCP Server by Xquik

Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.

作者：Xquik-dev·正在增长·★ 229·3天前更新

在云端运行✓ xquik.com

接入方法

Betterlytics

Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.

作者：betterlytics·正在增长·★ 193·3个月前更新

在云端运行✓ 服务方 · betterlytics.io

接入方法

BibiGPT YouTube Video Summarizer

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

作者：JimmyLv·正在增长·★ 141·18天前更新

在云端运行✓ 服务方 · bibigpt.co

接入方法

• Relaticle — 在云端运行，无需安装 · 不需要密钥
• ChatbotX — 在云端运行，无需安装 · 不需要密钥
• X (Twitter) MCP Server by Xquik — 在云端运行，无需安装 · 不需要密钥
• Betterlytics — 在云端运行，无需安装 · 需要密钥
• BibiGPT YouTube Video Summarizer — 在云端运行，无需安装 · 不需要密钥

作者的 README

{