Pipeline CRM MCP by usefulapi

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 마케팅 및 소셜 미디어

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

https://pipeline-crm.usefulapi.io/mcp

claude mcp add --transport http 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"
    }
  }
}

https://pipeline-crm.usefulapi.io/mcp

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 9일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• 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월 9일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 usefulapi.io 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  61ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 30개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

마케팅 및 소셜 미디어 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 3632개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 3632개 중 95%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 3632개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

{