CentralStationCRM MCP by usefulapi

할 수 있는 일

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

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 온라인 쇼핑몰 및 결제

설치

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

필요한 것

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

어떤 앱을 쓰세요?

https://centralstationcrm.usefulapi.io/mcp

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

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

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

https://centralstationcrm.usefulapi.io/mcp

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

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

할 수 있는 일

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

• centralstationcrm_get_current_user

  The CentralStationCRM user this API key belongs to: id, name, login email, the account (subdomain) it is signed in to, timezone. Use the user id to assign records or tasks. GET /user.

• centralstationcrm_list_users

  List the users of the CentralStationCRM account (id, name, email). Use the ids for responsible-user filters and for assigning records. GET /users.

• centralstationcrm_list_people

  List contact people. Optionally filter by tag and order by name, creation or last update. Use search_people to find a person by name, email or phone. GET /people.

• centralstationcrm_search_people

  Find people by last name, first name, email address or phone number (email and phone cannot be combined). Give at least one criterion. GET /people/search.

• centralstationcrm_get_person

  One person by id, optionally with related records (companies, deals, tags, tasks, email addresses, phone numbers, addresses). GET /people/{id}.

• centralstationcrm_list_companies

  List companies. Optionally filter by tag and order by name, creation or last update. Use search_companies to find one by name. GET /companies.

• centralstationcrm_search_companies

  Find companies by name. GET /companies/search.

• centralstationcrm_get_company

  One company by id, optionally with related records (people, deals, tags, tasks, contact details, addresses). GET /companies/{id}.

• centralstationcrm_list_deals

  List deals (sales opportunities) with value, state (open_0/25/50/75, won, lost), pipeline and stage ids, target date. Filter by company, responsible user, pipeline or state; order by date, value, state or name. GET /deals.

• centralstationcrm_search_deals

  Find deals by name. GET /deals/search.

• centralstationcrm_get_deal

  One deal by id, optionally with its tags, people, company, tasks and calendar events. GET /deals/{id}.

• centralstationcrm_get_deal_stats

  Number and total value of all deals (optionally only those with a tag), with the account currency. GET /deals/stats.

• centralstationcrm_list_deal_types

  List the deal types (pipelines) with their stages. Use the ids (and stage ids) to create deals and to move them between stages. GET /deal_types.

• centralstationcrm_list_projects

  List projects with state, target date and company. Filter by tag; order by date, state or name. GET /projects.

• centralstationcrm_search_projects

  Find projects by name. GET /projects/search.

• centralstationcrm_get_project

  One project by id, optionally with its tags, people, company, tasks and calendar events. GET /projects/{id}.

• centralstationcrm_list_tasks

  List tasks (to-dos, calls, emails, visits) of the account. Filter by open/closed state, due-date range and responsible user. GET /tasks.

• centralstationcrm_get_task

  One task by id. GET /tasks/{id}.

• centralstationcrm_list_notes

  List protocols: notes, logged emails and other history entries. Filter by the person, company, deal or project they belong to. GET /protocols.

• centralstationcrm_get_note

  One note / history entry by id. GET /protocols/{id}.

• centralstationcrm_list_calendar_events

  List calendar events (appointments, meetings) of the account. Filter by upcoming/old and date range. GET /cal_events.

• centralstationcrm_search_all

  Full-text search across people, companies, deals and projects for a term. GET /search.

• centralstationcrm_list_tags

  List all tag names used in the account. GET /tags/list.

• centralstationcrm_count_records

  Total number of people, companies, deals or projects (optionally only those with a tag). GET / /count.

• centralstationcrm_create_person

  WRITE: create a contact person (last name required), optionally with email addresses and phone numbers. Nothing is sent to the contact. POST /people.

• centralstationcrm_update_person

  WRITE: change fields of a person. Only the fields you give are sent; the rest stays. PUT /people/{id}.

• centralstationcrm_create_company

  WRITE: create a company. Nothing is sent to the contact. POST /companies.

• centralstationcrm_update_company

  WRITE: change fields of a company. Only the fields you give are sent. PUT /companies/{id}.

• centralstationcrm_create_deal

  WRITE: create a deal (sales opportunity). Use list_deal_types for pipeline and stage ids. Pipelines with a monetary value or target date need value and target_date (value_type defaults to total); the vendor says what is missing. Nothing is sent to the contact. POST /deals.

• centralstationcrm_update_deal

  WRITE: change fields of a deal, for example move it to another stage or set its state to won or lost. Only the fields you give are sent. PUT /deals/{id}.

• centralstationcrm_create_task

  WRITE: create a task (to-do, call, email, visit...) optionally attached to a person, company or deal and assigned to a user. Nothing is sent to the contact. POST /tasks.

• centralstationcrm_update_task

  WRITE: change a task, for example mark it done (finished = true), rename it or reschedule it. Only the fields you give are sent. PUT /tasks/{id}.

• centralstationcrm_create_note

  WRITE: add a note to the history of one or more people, companies, deals or projects. Nothing is sent to the contact. POST /protocols.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검

• ✓ 통과

  제작자와 저장소 일치

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

• … 아직 점검 안 함

  계속 관리되고 있음

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

• … 아직 점검 안 함

  라이선스 있음

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

• ✓ 통과

  엔드포인트 응답

  8ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

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

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

온라인 쇼핑몰 및 결제 카테고리의 다른 서버와 비교i

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

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

대안

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

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

제작자의 README

{