# JobScore MCP MCP > JobScore connects your AI agent to a full Applicant Tracking System (ATS). It lets you pull everything you need to manage hiring: job details, candidate profiles, team structures, and where applicants came from. Stop jumping between tabs and get the complete picture of your talent pipeline in one go. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** applicant-tracking, hiring, talent-acquisition, recruitment, candidate-management ## Description Look, when you're running recruitment, most of the data lives in silos. You might have a list of open jobs here, but then you need to check the status of candidates against those roles, cross-referencing which department owns that job or who on the team is supposed to interview them. This MCP lets your AI agent access JobScore's full API, so it can gather all that context for you. Your agent doesn't just read a name; it pulls the candidate's entire contact history and current status in one shot. Need to know which department owns this opening? Or where did the applicant originally find the job listing? You get all that data automatically streamed into your workflow, right through Vinkius. It means you spend time actually hiring people, not building complex reports or manually cross-referencing spreadsheets. ## Tools ### get_candidate Pulls a specific applicant's complete profile, including their status and contact history. ### get_job Retrieves the full job description and requirements for one specific opening. ### get_me Verifies your current connection status and user identity within JobScore. ### list_candidates Generates a list of all applicants, including their names and current application stage. ### list_departments Lists every department (e.g., Finance, Engineering) used to categorize jobs in the system. ### list_hiring_teams Retrieves a list of designated recruiters and hiring managers assigned to specific roles. ### list_jobs Returns titles, IDs, and departments for every active job opening in the account. ### list_locations Lists all physical office locations where the company hires people. ### list_sources Identifies and lists every channel (LinkedIn, Referral) used to source applicants. ### list_users Outputs a roster of all current users in the JobScore account for administrative checks. ## Prompt Examples **Prompt:** ``` List all open jobs in JobScore. ``` **Response:** ``` I'll fetch the list of active job postings from your JobScore account. ``` **Prompt:** ``` Show me the details for candidate ID '789'. ``` **Response:** ``` I'll retrieve the full profile and status for that specific candidate. ``` **Prompt:** ``` Check the hiring team for the 'Software Engineer' job. ``` **Response:** ``` I'll look up the members of the hiring team assigned to that position. ``` ## Capabilities ### View open positions and details Retrieves a complete catalog of active job listings, including requirements and team identifiers. ### Monitor the entire applicant pool Lists every candidate in your system, showing their current stage and unique IDs for tracking. ### Pull detailed candidate profiles Gets a specific person's full application history, resume highlights, and contact information. ### Map internal team structure Lists all users, departments, and dedicated hiring teams within the company account. ### Track sourcing channels Identifies exactly which source (like a referral or job board) brought in each candidate. ## Use Cases ### A new role is opening, but the hiring team isn't assigned. The agent gets a job ID from `list_jobs`, then calls `get_job` to get requirements. The next step is asking who should own it; the agent runs `list_hiring_teams` and identifies the correct department using `list_departments`. ### You suspect a job opening isn't pulling in enough applicants. The agent uses `list_sources` to check where candidates *are* coming from. If that data is good, but the results are low, it prompts you to run `get_job` for more details and potentially adjust the listing. ### You need a quick roster of all available contacts for an internal meeting. The agent runs `list_users` to get names and roles, then uses that list to check if specific team members are assigned to relevant jobs via `list_hiring_teams`. ### A candidate's status seems inconsistent across different systems. The agent runs `get_candidate` first. If the data is still unclear, it uses `list_locations` to confirm if the candidate was applying for a role in your main office or one of your smaller branches. ## Benefits - Stop guessing where a candidate came from. By calling `list_sources`, you instantly know if they were a referral, which helps measure your best channels. - You never have to manually check who is responsible for an open role again. Just ask the agent to use `list_hiring_teams` and get the assigned managers immediately. - Need to compare job requirements against internal structure? Call `list_departments` first, then use that data when running `get_job` to ensure you're posting in the right business unit. - When evaluating a candidate, don't just rely on the application form. Use `get_candidate` to pull their full contact history and resume highlights for complete due diligence. - Need an overview of your entire talent funnel? Running `list_candidates` gives you names and stages across all roles without needing multiple manual searches. ## How It Works The bottom line is that your agent combines these separate data points—jobs, people, and teams—into one actionable summary. 1. First, tell your agent to get all current open jobs using the `list_jobs` tool. This gives you the core set of opportunities. 2. Next, run `list_candidates` to pull a list of applicants and their IDs; then, use those IDs with `get_candidate` to gather detailed profiles for anyone needing review. 3. Finally, if you need context, call `list_hiring_teams` or `list_departments`. This provides the organizational structure needed to assign next steps. ## Frequently Asked Questions **How do I find out if my agent can pull all open jobs using list_jobs?** Yes, `list_jobs` returns the titles and IDs for every active opening. This is your starting point when you want to know what roles are currently available in the system. **Can I use get_candidate to check an applicant's status?** Absolutely. `get_candidate` pulls their full profile, which includes their current application stage and contact history. It’s better than just looking at the main dashboard. **What is the difference between list_departments and list_users?** Departments define business units (like 'Marketing' or 'Engineering'), while `list_users` lists actual people who are logged into the account. One defines the function, the other defines the person. **How do I track where candidates came from using list_sources?** `list_sources` shows you all the channels—like 'LinkedIn' or 'Referral'—that applicants used to apply. It’s essential for measuring your recruiting effort. **How do I verify my connection status using the `get_me` tool?** It returns your current authenticated user information. This confirms that your AI agent has successfully connected and is authorized to access the JobScore data for your account. **What job details can I retrieve when I use `get_job`?** You get comprehensive data including the full job description, specific requirements, and identifiers for the hiring team. This lets you pass detailed information about a single opening to your workflow. **How do I monitor all applicants in my pipeline using `list_candidates`?** This tool provides a list of every candidate, including their name, current stage in the process, and unique ID. It's essential for quickly surveying your entire talent pool. **Can I identify who is involved with hiring using `list_hiring_teams`?** Yes, this lists all associated hiring teams, helping you pinpoint specific recruiters and managers tied to certain roles. It's key for coordinating job-specific personnel. **How do I get JobScore API credentials?** Log in to your JobScore account, navigate to Admin > Integrations, and generate a Personal Access Token. **Does it support departments and locations?** Yes, you can list all configured departments and office locations using this MCP. **Can I see candidate details?** Yes, the list_candidates and get_candidate tools provide access to your applicant data.