Taleez MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://taleez.usefulapi.io/mcp

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

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

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

https://taleez.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• taleez_list_jobs

  List the job postings of the company (id, label, status DRAFT/PUBLISHED/DONE/SUSPENDED, contract, location, recruiter, unit, tags, visibility, public URL). Filter by status, contract, unit, city, tag, company label or visibility; sort by creation or publication date. Job and prof

• taleez_get_job

  One job posting by id with its full details: descriptions, contract, location, recruiter, unit, tags, custom properties, public and application URLs. GET /0/jobs/{id}.

• taleez_get_job_steps

  The recruitment pipeline steps of a job in order (id, name, order). Use them to read where each candidate stands. GET /0/jobs/{id}/steps.

• taleez_get_job_statuses

  The status history of a job: each change (date timestamp, status DRAFT/PUBLISHED/SUSPENDED/DONE). GET /0/jobs/{id}/statuses.

• taleez_get_job_questions

  The questions candidates answer when applying to a job (id, label, type, required, choices). GET /0/jobs/{id}/questions.

• taleez_get_job_filters

  The total number of jobs and the job counts per status, contract, city, tag and company label (only values with at least one job). A quick overview of the hiring activity. GET /0/jobs/filters.

• taleez_list_job_properties

  The custom job properties defined in the account (id, name, type, choices). GET /0/job-properties.

• taleez_list_candidates

  List the candidates in the company (id, name, mail, phone, language, location, social links, unit, creation date). Filter by exact e-mail address to find one person. Custom properties only with with_props. Candidates contain personal data: use it only for the user's own recruitin

• taleez_get_candidate

  One candidate by id: name, mail, phone, language, location, social links, unit, CV link and custom properties. GET /0/candidates/{id}.

• taleez_get_candidate_applications

  Where a candidate stands: every application or association (type SPONTANEOUS, APPLICATION_TO_A_JOB, ASSOCIATED_TO_A_JOB...) with the job id, current pipeline step, rejected/hired dates and the step history. GET /0/candidates/{id}/applications.

• taleez_get_candidate_properties

  The custom property values of a candidate (property id, name key, type, value or choices). GET /0/candidates/{id}/properties.

• taleez_get_candidate_pools

  The talent pools a candidate belongs to (pool id, name, date added, referrer). GET /0/candidates/{id}/pools.

• taleez_get_candidate_documents

  The documents attached to a candidate (CV, cover letter...): id, name, date, size and file URL. GET /0/candidates/{id}/documents.

• taleez_get_candidate_events

  The events (interviews, calls, meetings) scheduled with a candidate: subject, start/end, location, meeting URL, attendees. GET /0/candidates/{id}/events.

• taleez_list_candidate_properties

  The custom candidate properties defined in the account (id, name, type, choices, disabled). Use the ids with taleez_set_candidate_properties. GET /0/candidate-properties.

• taleez_list_pools

  List the talent pools of the company (id, name, dates, recruiter). GET /0/pools.

• taleez_list_pool_candidates

  The candidates in one talent pool. Custom properties only with with_props. GET /0/pools/{id}/candidates.

• taleez_list_recruiters

  List the recruiters (users) of the company. Use the ids to read who owns a job or to credit a new candidate. GET /0/recruiters.

• taleez_list_units

  List the units (entities, subsidiaries, sites) of the company. Use the ids to filter jobs. GET /0/units.

• taleez_list_events

  List the company's calendar events (interviews, meetings): subject, start/end timestamps, location, meeting URL, job id, attendees. GET /0/events.

• taleez_create_candidate

  WRITE: add a new candidate to the Taleez database (first and last name required; the e-mail, if given, must be unique in the company). Creates a record only: the candidate is not attached to a job and no e-mail is sent by this call. Not idempotent: calling twice with no mail crea

• taleez_update_candidate

  WRITE: change a candidate's name, e-mail, phone, social links or location. The current record is read first and unchanged name, mail and phone are sent back, so only what you pass changes (Taleez' update endpoint otherwise needs first and last name). Social links and location, wh

• taleez_set_candidate_properties

  WRITE: set custom property values on a candidate. For a property without choices pass value (DATE as yyyy-MM-dd); for a property with choices pass choices (choice ids, see taleez_list_candidate_properties). An empty choices list removes all selected choices unless append_choices

• taleez_add_candidates_to_pool

  WRITE: add existing candidates to a talent pool (see taleez_list_pools). Adding a candidate already in the pool is harmless. No message is sent. POST /0/pools/{id}/candidates.

• taleez_add_candidates_to_job

  WRITE: associate existing candidates to a job so they appear in its recruitment pipeline (the vendor's 'add candidates to a job'; this is an association made by the recruiter, not a candidate application, and this call sends no message). Pass location_id for a job with several lo

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 1313 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 25 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32455 servers in this category
• Published to the registry more recently than 97% of the other 32455 servers in this category
• Basic checks equal to or better than 100% of the other 32455 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{