CATS MCP by usefulapi

할 수 있는 일

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

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 기타

설치

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

필요한 것

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

어떤 앱을 쓰세요?

https://cats-ats.usefulapi.io/mcp

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

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

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

https://cats-ats.usefulapi.io/mcp

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

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

할 수 있는 일

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

• cats_get_site

  The CATS site (account) this API key belongs to: id, mode (recruiter or employer) and subdomain. GET /site.

• cats_list_users

  List the CATS users (recruiters) with id, name, title and access level. Use the ids as owner or assignee. GET /users.

• cats_list_candidates

  List candidates (personal data: name, emails, address, employer, skills, notes), one page at a time, max 100 per page. Use cats_search_candidates or cats_filter_candidates to find specific people. GET /candidates.

• cats_get_candidate

  One candidate by id (personal data). GET /candidates/{id}.

• cats_search_candidates

  Free-text search over candidates (name, email, skills, resume text...), paged. GET /candidates/search?query=.

• cats_filter_candidates

  Filter candidates by fields (read-only, although it is a POST): first_name, last_name, title, emails.primary, address.city/state/postal_code, country_code, current_employer, key_skills, notes, dates (date_created, date_modified), owner_id, is_hot... Each condition is {field, filt

• cats_list_candidate_pipelines

  The jobs a candidate is in the pipeline for, with rating, workflow and current status id. GET /candidates/{id}/pipelines.

• cats_list_candidate_activities

  The activity log of a candidate (calls, meetings, notes, pipeline changes), paged. GET /candidates/{id}/activities.

• cats_list_candidate_tasks

  Tasks attached to a candidate. GET /candidates/{id}/tasks.

• cats_list_candidate_attachments

  File names, sizes and whether each file is a resume, for a candidate's attachments. Metadata only: file contents are never downloaded. GET /candidates/{id}/attachments.

• cats_list_jobs

  List job orders with title, location, company, recruiter, status and workflow ids, dates. Paged. GET /jobs.

• cats_get_job

  One job order by id, with its description. GET /jobs/{id}.

• cats_search_jobs

  Free-text search over job orders, paged. GET /jobs/search?query=.

• cats_list_job_pipelines

  The candidates in the pipeline of a job: pipeline id, candidate id, rating and current status id. Paged. GET /jobs/{id}/pipelines.

• cats_list_job_statuses

  The statuses a job order can have (Active, OnHold, Closed...). GET /jobs/statuses.

• cats_list_pipelines

  List candidate-to-job pipelines (candidate id, job id, rating, workflow id, status id), paged. GET /pipelines.

• cats_get_pipeline

  One pipeline (a candidate on a job) by id. GET /pipelines/{id}.

• cats_filter_pipelines

  Filter pipelines by id, candidate_id, job_id, status_id, rating, date_created or date_modified (read-only, although it is a POST). Each condition is {field, filter, value}. Paged. POST /pipelines/search.

• cats_get_pipeline_status_history

  The status changes of a pipeline over time (status, who, when). GET /pipelines/{id}/statuses.

• cats_list_workflows

  The pipeline workflows (sets of statuses such as Contacted, Interviewing, Offered). GET /pipelines/workflows.

• cats_list_workflow_statuses

  The statuses of one pipeline workflow (id, title, prerequisites, triggers). Use the ids with cats_change_pipeline_status. GET /pipelines/workflows/{id}/statuses.

• cats_list_companies

  List client companies (name, address, website, owner), paged. GET /companies.

• cats_get_company

  One company by id. GET /companies/{id}.

• cats_search_companies

  Free-text search over companies, paged. GET /companies/search?query=.

• cats_list_contacts

  List client contacts (personal data: name, title, emails, company), paged. GET /contacts.

• cats_get_contact

  One client contact by id (personal data). GET /contacts/{id}.

• cats_search_contacts

  Free-text search over client contacts, paged. GET /contacts/search?query=.

• cats_list_tasks

  List tasks (description, priority 1-5, due date, assignee, completion, the record it is about), paged. GET /tasks.

• cats_get_task

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

• cats_list_activities

  The site-wide activity log (calls, emails logged, meetings, notes) with the record each is about, paged. GET /activities.

• cats_add_candidate_activity

  WRITE: Requires confirm:true. log an activity (a call, meeting, note...) on a candidate's record. It only records the entry in CATS: no email/SMS-send request is made, even for type 'email' or 'text_message'. Creates a new entry each time (not idempotent). POST /candidates/{id}/a

• cats_create_task

  WRITE: Requires confirm:true. create a task in CATS, optionally about a candidate, contact, company or job and assigned to a user. Creates a new task each time (not idempotent); CATS may notify the assignee. POST /tasks.

• cats_change_pipeline_status

  WRITE: Requires confirm:true. change the status of a pipeline (move a candidate to another stage of a job's workflow, e.g. Interviewing, Offered, Rejected). Get the pipeline id from cats_list_candidate_pipelines and the status id from cats_list_workflow_statuses. Requires confirm

• cats_create_candidate

  WRITE: Requires confirm:true. create one candidate record (personal data) with name, optional contact details and notes. Refuses when CATS finds a duplicate (check_duplicate=true, the default). Creates a new record each time (not idempotent); no email-send request is made to the

기본 점검i

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

• ✓ 통과

  제작자와 저장소 일치

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

• … 아직 점검 안 함

  계속 관리되고 있음

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

• … 아직 점검 안 함

  라이선스 있음

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

• ✓ 통과

  엔드포인트 응답

  50ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

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

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

기타 카테고리의 다른 서버와 비교i

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

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

대안

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

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

제작자의 README

{