Jobtoolz MCP for AI. Manage candidate flow and job data automatically.

Q: How do I use listjobs to see all open positions?

listjobs provides a list of every active job opening, including the title and department ID. This is your starting point for finding what roles are available right now.

Q: What does getcandidate do?

getcandidate retrieves a deep profile for one person. It pulls contact details, application history, and any custom fields attached to their record.

Q: How can I audit where candidates came from using Jobtoolz MCP?

Use the listsources tool. This lists every recruitment source configured in your account—like 'Indeed' or 'Company Website'—so you know where to focus your marketing efforts.

Q: I need to find all jobs for a specific location; what should I use?

Run listlocations first to confirm the exact ID. Then, you can cross-reference that list against listjobs to filter only those roles open at your desired office.

Q: How do I check what stages are in my company's hiring pipeline using liststages?

liststages returns all configured pipeline steps. This lets you see the full flow, like 'Applied,' 'Interview,' or 'Offer.' Use this to map out your entire company hiring process before automating workflows.

Q: If I need to know which hiring managers are set up, how do I use the listusers tool?

listusers gives you a list of all organization accounts. You can check who the admins or specific hiring managers are, which is essential for managing permissions and knowing who owns what data.

Q: What data does the getjob tool return that helps me analyze specific job needs?

getjob retrieves much more than just a title. It provides detailed descriptions, required qualifications, and internal status markers for deep analysis of any single role.

Q: I need to filter candidates or jobs by business area; how do I use listdepartments?

listdepartments retrieves all available departments (like Sales or R&D). This is necessary if you want to narrow down your search results and focus only on records associated with a specific business unit.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

Jobtoolz provides a full API connection to recruitment management data. Use this MCP to automate candidate tracking, view open positions, and map out your entire hiring pipeline programmatically.

Need to check applicant status or cross-reference job details? This tool handles it all.

What your AI can do

Get candidate

Pulls deep data on one applicant, including their contact info and full application record.

Get job

Retrieves all requirements and status information for a single job opening.

List candidates

Generates an overview list of every candidate in the system, showing their ID and current pipeline stage.

+ 7 more capabilities included

Look Up Specific Candidate Profiles

Retrieve full details, contact info, and the complete history of any single applicant.

Analyze Job Requirements

Get detailed descriptions, necessary qualifications, and internal status for a specific job role.

Map Out Applicant Flow

Pull lists of all candidates currently in the system to monitor overall applicant volume and status.

Audit Business Structure

List departments, locations, or recruitment sources to filter data by business unit or geography.

Check Pipeline Statuses

Get all configured pipeline stages and tags so your agent knows the official hiring process steps.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

Jobtoolz: 10 Tools for Recruitment Management

Use these tools to systematically gather, filter, and audit all structured data related to your company's job openings and candidate pipeline.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Jobtoolz on Vinkius

Get Candidate

Pulls deep data on one applicant, including their contact info and full application record.

Get Job

Retrieves all requirements and status information for a single job opening.

List Candidates

Generates an overview list of every candidate in the system, showing their ID and...

List Departments

Provides a comprehensive list of all departments used within your organization's...

List Jobs

Lists every currently active job opening, including the title and which department...

List Locations

Returns a list of all office locations where jobs are open.

List Sources

Lists all ways candidates entered the system (e.g., Indeed, Company Website) for auditing purposes.

List Stages

Shows every configured stage in your hiring workflow (Applied, Interview, Offer).

List Tags

Lists all custom tags used to categorize or filter candidate records.

List Users

Retrieves a list of internal users, such as administrators or hiring managers.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The Jobtoolz integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "jobtoolz": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the Jobtoolz tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"jobtoolz": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with Jobtoolz, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Jobtoolz. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Tracking candidates means constant, tedious cross-referencing.

Today, finding out exactly where a candidate stands requires clicking between dozens of tabs. You check the job posting for requirements, then go to the candidate profile for their history, and finally open another tab just to see which department they were assigned to. It's copy-pasting IDs and switching views until you lose your train of thought.

With this MCP, that sequence disappears. Your agent handles it all in one conversation. You ask about a specific applicant, and the system pulls together their full record—their history, their current job status, and even which department they were originally assigned to. You get clean data, every time.

Jobtoolz MCP: Access all structured candidate and job data.

You no longer have to manually check the 'Open Jobs' tab for titles, then switch to the departments list to see which business unit it belongs to. The `list_jobs` tool combines these steps. It gives you a single output containing all active job IDs and their corresponding department names.

What changes is that your agent treats this entire catalog like its own database connection point. You don't just 'see' the data; you can use it immediately to build workflows.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

This connector lets your agent manage the messy parts of recruiting. Instead of juggling spreadsheets and logging into multiple tabs just to track a candidate's movement, you get direct access to core recruitment data. You can list every open position, pull up a candidate’s entire application history, or check which department they belong to—all through simple API calls.

If your job is automating the hiring funnel, this MCP has what you need. By connecting Jobtoolz via Vinkius, you give your AI client the ability to treat raw recruitment data like it's part of its natural knowledge base. You can audit everything from how a candidate arrived (the source) to which stage they are currently in.

It turns complex HR workflows into simple commands for your agent.

Built · Hosted · Managed by Vinkius Jobtoolz - Manage Candidates and Job Pipeline Data

Server ID 019d75bd-9f9b-73af-a6a7-5edc101f20bb

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is that it gives your AI client a structured way to ask the hiring platform for specific information without needing to write any complicated code.

Your agent determines it needs data, for instance, a list of active roles.

It calls the appropriate tool (like list_jobs), which sends a request to Jobtoolz's API endpoint.

The MCP receives structured JSON data containing job titles, IDs, and departments, which your agent then uses.

What Changes When You Connect

Stop manually checking statuses. Using list_candidates lets your agent monitor the entire applicant pool, so you always know who's where in the pipeline.

No more guessing about roles. You can check a specific role’s details using get_job, ensuring your AI client has all mandatory requirements before drafting job descriptions.

Audit hiring effectiveness instantly. Pulling data from list_sources tells you exactly which channels bring in the most qualified leads, saving time on marketing spend.

Filter candidates accurately by business unit or geography using list_departments and list_locations. This narrows down your search results to only relevant talent pools.

Understand process bottlenecks. By checking all configured stages with list_stages, you can spot if the 'Interview' phase is slowing everything down.

See it in action

01 01

Auditing a specific hiring channel

A recruiter needs to know if their company website or Indeed has been the primary source of leads this quarter. The agent uses list_sources to pull all origins, allowing the user to immediately filter and review only candidates from the desired location.

02 02

Finding roles for a new department

A hiring manager wants to see what open positions exist in R&D but not Sales. They ask the agent to combine list_departments with list_jobs, generating a precise list of job IDs they can then use to pull candidate requirements.

03 03

Reviewing an applicant's full history

A team member needs to vet Candidate ID 'XYZ'. They ask the agent to run get_candidate and get a full report, including their contact details and every job they applied for in the past.

04 04

Cross-referencing candidate tags

The TA specialist needs all candidates who are marked 'Senior' and whose current status is 'Interview'. The agent uses list_tags to confirm valid tags, then runs a combined search on the candidate list.

The honest tradeoffs

Searching for job details manually

Anti-pattern

The user remembers a job title but can't find its specific ID or detailed requirements across different tabs in the dashboard.

The Fix

Instead of clicking through, ask your agent to first run list_jobs to get all IDs. Then, feed that ID into get_job for immediate access to the full description and status.

Assuming candidate data is current

Anti-pattern

A manager assumes a candidate who applied three months ago still has active contact info or hasn't changed departments.

The Fix

Always use get_candidate to pull the latest, verified details. This ensures your agent gets the absolute most recent record of their application and status.

Trying to build a job list by hand

Anti-pattern

Manually checking the 'Open Jobs' tab and writing down every title and its corresponding department ID.

The Fix

Let the MCP run list_jobs. This single call provides all active roles, their titles, and their associated departments in one structured output.

When It Fits, When It Doesn't

Use this MCP if your workflow requires querying specific, structured facts about hiring—like 'What is the status of Candidate X?' or 'Which jobs exist in Department Y?'. It's for data retrieval. Don't use it if you just need to write a general email update; for that, your agent can handle plain text generation. If you only need high-level metrics (e.g., total applicants), list_candidates is often enough. But if you need to act on the data—like pulling contact details or specific job requirements—this MCP gives you the power to do it.

Questions you might have

How do I use `list_jobs` to see all open positions? +

list_jobs provides a list of every active job opening, including the title and department ID. This is your starting point for finding what roles are available right now.

What does `get_candidate` do? +

get_candidate retrieves a deep profile for one person. It pulls contact details, application history, and any custom fields attached to their record.

How can I audit where candidates came from using Jobtoolz MCP? +

Use the list_sources tool. This lists every recruitment source configured in your account—like 'Indeed' or 'Company Website'—so you know where to focus your marketing efforts.

I need to find all jobs for a specific location; what should I use? +

Run list_locations first to confirm the exact ID. Then, you can cross-reference that list against list_jobs to filter only those roles open at your desired office.

How do I check what stages are in my company's hiring pipeline using `list_stages`? +

list_stages returns all configured pipeline steps. This lets you see the full flow, like 'Applied,' 'Interview,' or 'Offer.' Use this to map out your entire company hiring process before automating workflows.

If I need to know which hiring managers are set up, how do I use the `list_users` tool? +

list_users gives you a list of all organization accounts. You can check who the admins or specific hiring managers are, which is essential for managing permissions and knowing who owns what data.

What data does the `get_job` tool return that helps me analyze specific job needs? +

get_job retrieves much more than just a title. It provides detailed descriptions, required qualifications, and internal status markers for deep analysis of any single role.

I need to filter candidates or jobs by business area; how do I use `list_departments`? +

list_departments retrieves all available departments (like Sales or R&D). This is necessary if you want to narrow down your search results and focus only on records associated with a specific business unit.

How do I get Jobtoolz API credentials? +

Does it support departments and locations? +

Yes, you can list all configured departments and office locations using this MCP.

Can I see pipeline stages? +

Yes, the list_stages tool provides access to your recruitment pipeline configuration.

Connect to your AI in seconds.

Get candidate

Get job

List candidates

Jobtoolz: 10 Tools for Recruitment Management

Make your AI actually useful.

Get Candidate

Get Job

List Candidates

List Departments

List Jobs

List Locations

List Sources

List Stages

List Tags

List Users

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Tracking candidates means constant, tedious cross-referencing.

Jobtoolz MCP: Access all structured candidate and job data.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

Auditing a specific hiring channel

Finding roles for a new department

Reviewing an applicant's full history

Cross-referencing candidate tags

The honest tradeoffs

Searching for job details manually

Assuming candidate data is current

Trying to build a job list by hand

When It Fits, When It Doesn't

Questions you might have