AI assistants · MCP

Use Zignaltalent from ChatGPT, Claude and other AI assistants

Zignaltalent is also a Model Context Protocol (MCP) server. An assistant that supports MCP connects once, then searches jobs and consultants, posts, checks matches and requests resumes as you, with exactly the same rules as the website. Your ATS stays your system of record.

Connect

Add Zignaltalent as a remote MCP server in your assistant and sign in when it asks. The address is:

MCP server address

https://www.zignaltalent.com/api/mcp
  1. OAuth (recommended). The assistant opens a Zignaltalent sign-in page; you approve it for your account and it receives its own token, which you can revoke in Settings → Integrations at any time.
  2. API key. Assistants and tools that cannot sign in use a personal key from Settings → Integrations, sent as Authorization: Bearer <key>.

Works with ChatGPT, Claude, Cursor, VS Code, Windsurf and any other client that supports remote MCP servers over HTTP. Discovery documents are at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.

Things to ask

  • “Find C2C Java consultants in Texas with a green card”
  • “Post this requirement and tell me who matches: <paste the client email>”
  • “Which of my consultants fit the open React jobs in Dallas?”
  • “Request the resume for CD-TAL-… and let me know when it is approved”
  • “What changed on my posts since yesterday?”

The 21 tools

Each tool does one thing the website does, on the desk you are signed in as (recruiter, bench sales or job seeker). Tools marked “reads only” change nothing.

Look around

Who am Iwhoami · reads only
The connected account: name, company, desk (recruiter, bench sales or job seeker) and how much of each free limit is used. Call this first.
Search open jobssearch_jobs · reads only
Live IT jobs on the network (contract and full-time, posted by US staffing firms). Filter by words, state, city, work mode or accepted visa. Returns public details and post codes; client names stay hidden.
Search available consultantssearch_consultants · reads only
Consultants that staffing firms have on the market. Filter by words, skills, state, city, visa or start date. Names and contact details are never shown; ask for a resume with request_resume.
My postslist_my_posts · reads only
Your own posts (jobs, consultants or availability) with status, expiry and match counts.
What changedget_updates · reads only
Events since a time or since your last check, oldest first: new matches, resume requests and answers, submission updates, messages and connections. Pass the returned nextCursor next time to get only newer events. Does not mark anything read.

Post and match

Post a jobpost_job
Publishes a job (recruiter desk). It goes live and is matched with available consultants right away. Requires title, skills and accepted work authorization; nothing else is guessed.
Post a consultantpost_consultant
Puts a consultant on the market (bench sales desk) so they are matched with live jobs. Requires title, skills, years of experience and work authorization. Do not include names or contact details.
Import from an ATSimport_from_ats
Sends job or candidate records exactly as your ATS stores them. Understood ATSs: bullhorn, ceipal, jobdiva, avionte, crelate, zoho_recruit, loxo, recruitcrm, jobadder, vincere, pcrecruiter, manatal, catsone, recruiterflow, targetrecruit, greenhouse, lever, workday, icims, smartrecruiters, ashby, workable, jazzhr, bamboohr, breezy, teamtailor, jobvite, oracle, successfactors, recruitee, generic ("generic" matches common field names from any other ATS, and schema.org JobPosting). Complete records are published; records missing something a post needs are saved as a draft and the missing fields are listed. Re-sending the same record updates the post instead of posting it twice; a filled, closed or on-hold status closes or pauses it. Pass a connection id from Settings → Integrations to use that connection's field mapping and defaults.
Pause, resume, close or extend a postupdate_post
Changes one of your posts: pause (hide from matching), resume, close (with a reason), or extend (adds time, up to 3 times).
Matches for a postget_matches · reads only
Ranked matches for one of your posts, with the fit score, why it fits, the screening checks and where each match stands (requested, shortlisted, submitted…).

Resumes and consent

Request a resumerequest_resume
Asks the owner of a consultant post for the full resume (recruiter desk). The owner approves or declines; contact details are shared only after approval. Counts against the monthly request limit.
Resume requestslist_requests · reads only
Resume requests you sent (box "out") or that wait for your answer (box "in"), with status.
Approve or decline a requestanswer_request
Answers a resume request sent to you. Approving shares the resume with the requester; declining can include a short reason.

Submissions and the pipeline

My consultantslist_my_consultants · reads only
Your bench (bench sales desk): each consultant's id (used by submit_consultant), role, skills, work authorization, resume and live post. Give a job code to also see how well each one fits that job and who is already submitted to its client.
Submit a consultant to a jobsubmit_consultant
Submits one of your consultants to a live job (bench sales desk). You must confirm you have the consultant's permission. The job's recruiter gets view access to the resume.
Submissionslist_submissions · reads only
Consultants submitted to your jobs and the ones you submitted, with their stage (submitted, reviewing, interview, offer, placed).
Pipelineget_pipeline · reads only
Your pipeline board: matches by stage (matched, shortlisted, in discussion, outcome).
Move a submission alongupdate_submission
Moves a submission to its next stage. Job owner: reviewing, interview (with interviewAt), offer, placed (with startDate and finalRate), or rejected (with a reason). Submitter: withdrawn (with a reason). The other side is notified, exactly as on the website.

Conversations

Conversationslist_conversations · reads only
Your conversations (opened by a shortlist, a submission or a connection), newest first, with who they are with, the post, the last message and unread count.
Read a conversationread_conversation · reads only
The latest messages in one of your conversations, oldest first, marked "you" or "them". Opening it marks it read, as on the website.
Send a messagesend_message
Writes in one of your existing conversations (only people you are already talking with through a match, a submission or a connection). The other side is notified.

The same rules as the website

  • A connected assistant acts only as its owner, on the owner’s desk, within the owner’s free-plan limits.
  • Names, contact details and full resumes are shared only after the consultant or their firm approves a request; the assistant cannot read them before that.
  • Duplicate protection still applies: one firm per consultant per end client for 90 days.
  • Posts still expire on their own: jobs after 21 days, urgent jobs after 72 hours, consultants after 90 days.
  • Tokens and keys can be revoked at any time in Settings → Integrations; deleting the account revokes them all.

More on how it fits beside an ATS: Use Zignaltalent from your ATS and your AI assistant. Questions: the FAQ.