Automate candidate and job pipeline management.
Claude
ChatGPT
Cursor
Gemini
Windsurf
VS Code
JetBrains
Vercel
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
The JOIN MCP lets your agent manage the entire candidate lifecycle right from your workflow. List open job postings, pull detailed profiles for candidates, and track application statuses automatically.
It handles everything needed to automate talent acquisition.
What your AI can do
Get application
Retrieves all details for one specific job application, including answers and notes.
Get candidate
Pulls the full profile data for an individual candidate's record.
Get job
Gets the description, requirements, and metadata for a specific job posting.
It retrieves a list of all current job postings and their status within the system.
You can pull complete profiles for any specific candidate, including contact information.
This pulls all data related to a single job application, such as answers or internal notes.
It lists every department within the organization for filtering jobs or grouping users.
The system provides a list of all authenticated user accounts in your JOIN instance.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 CompatibleWaiting for input…
JOIN: Recruitment Tools (10 Tools)
These tools let you query everything from candidate profiles to open jobs, making your entire talent acquisition process automated.
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 Join on VinkiusGet Application
Retrieves all details for one specific job application, including answers and notes.
Get Candidate
Pulls the full profile data for an individual candidate's record.
Get Job
Gets the description, requirements, and metadata for a specific job posting.
Get Me
Verifies your connection identity and retrieves basic account details.
List Applications
Lists multiple applications across the system for monitoring applicant flow.
List Candidates
Returns a comprehensive list of all candidates, including their contact info and job associations.
List Departments
Lists every functional department (e.g., Engineering, Sales) within the organization.
List Jobs
Provides an overview of all job postings by title and current status.
List Locations
Retrieves a list of physical locations where jobs are available or based.
List Users
Lists every user account connected to your JOIN system for access auditing.
Connect to your AI in seconds. 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.
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
Make Your AI Do More
Start with Join, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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 JOIN. 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
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.
The Pain of Manual Talent Data Aggregation
Today, if you need to know who applied for a job and what their status is, you open JOIN. You pull up the Job Posting page, then click through dozens of candidate profiles. To get a summary report that includes notes or specific form answers, you copy-paste data into an Excel sheet, hoping nothing gets missed in the transfer process.
With this MCP, your agent handles the clicks. You ask for the status and key details, and it executes all those lookups automatically. The result isn't a spreadsheet—it’s actionable data delivered directly to your conversation window.
get_candidate: Direct Access to Vetted Profiles
Manually checking a candidate requires opening the profile, finding their contact info, and then reading through notes attached to previous applications. This process is slow, and you often have to cross-reference multiple screens just to build a full picture of fit.
Now, calling get_candidate delivers all that vetted information in one structured response. You get the whole file instantly—no clicking around needed.
What your AI can actually do with this
This MCP connects your AI client directly to the core functions of the JOIN platform. Instead of jumping between tabs or exporting CSVs just to get a hiring status update, you tell your agent what you need done. You can pull detailed job descriptions, run lists of active candidates, and fetch specific application data points like internal notes or form answers.
It’s designed for people who manage high-volume hiring pipelines.
For example, you can ask your system to identify all open roles in a certain department, then find the top three candidates associated with those jobs, and finally check their most recent activity. This MCP provides that data structure right out of the gate. By connecting through Vinkius, your agent gains access to this entire catalog, making complex recruiting tasks feel like simple conversation.
019d75bd-d03e-7155-847a-1d6657be1131 Here's how it actually works
The bottom line is that your AI client executes complex recruiting queries using simple commands.
You tell your agent the goal, for example: 'Show me the status of applications for candidates in Sales.'
Your agent identifies the necessary steps, calling tools like list_departments and then get_application to gather all required data points.
The system returns a consolidated summary containing only the filtered candidate details you asked for.
Who is this actually for?
HR Tech Leads and Operations Engineers who spend too much time manually compiling talent reports. If you're tired of juggling spreadsheets to track applications, this MCP streamlines the process.
Uses the MCP daily to vet specific candidates by calling get_candidate and list_applications to see who needs a follow-up.
Manages departments and user accounts, using tools like list_departments and list_users to audit access permissions across the company.
Needs a quick overview of the hiring pipeline, calling list_jobs repeatedly to report on open roles by location or department.
What Changes When You Connect
Stop manually checking statuses. Use list_applications to get a real-time count of recent applicants, letting your agent filter them by status immediately.
Vet candidates faster than ever. Instead of opening multiple tabs, call get_candidate for full details and use get_job to compare their skills directly against the job requirements.
Filter job roles precisely. If you need all open jobs in a specific functional area, list_departments lets your agent narrow down the search before calling list_jobs.
Streamline onboarding data capture. Need to know who's on staff? Use list_users to audit account access and verify that every role has the correct permissions.
Manage entire cohorts. When you need a mass report, call list_candidates to pull profiles for everyone and then use get_application to cross-reference their best work.
See it in action
Hiring Manager needs a shortlist of qualified people.
A hiring manager asks their agent, 'Find me the top 5 candidates for the Senior Dev role.' The agent calls get_job to grab requirements, then uses list_candidates and get_candidate on the best matches, delivering a vetted shortlist.
Recruiter needs to segment applicants by location.
The recruiter asks the agent to compile all applications from California. The agent calls list_locations first to validate 'California,' then uses list_applications to pull only those records tied to that area.
HR Ops needs an audit of job structure.
The operations manager asks the agent, 'What departments are we hiring for right now?' The agent calls list_departments and then uses list_jobs, filtering the results by department name to give a clean report.
Checking system health after an integration failure.
The user asks the agent to verify which accounts exist in JOIN. The agent runs list_users and calls get_me just to confirm connection stability, making it easy to spot access gaps immediately.
The honest tradeoffs
Asking for 'everything about jobs'.
Prompting the agent with: 'Show me all job data and candidate data.' This returns a massive, unusable dump of information.
Be specific. First, run list_jobs to get titles, then use get_job on only the ID you care about. Always narrow the scope first.
Comparing candidates without history.
Calling get_candidate for two people but forgetting their application status; you can't tell who is actually in play.
Always pair get_candidate with list_applications to make sure the candidate has an active, recent record.
Ignoring organizational structure.
Trying to filter jobs by a department name that doesn't exist in JOIN.
Always run list_departments first. This validates valid filtering parameters before running list_jobs.
When It Fits, When It Doesn't
Use this MCP if your workflow requires structured data about the hiring pipeline, such as comparing candidate profiles to job requirements or tracking status changes for multiple applicants. It's essential when you need to query specific records (e.g., get_application) after first gathering a list of identifiers (e.g., list_candidates). Don't use this if your goal is simply drafting external emails; then, an email writing tool works better. If all you need is a simple count of job roles without any details, basic reporting tools suffice—you don't need the full depth of get_job.
Questions you might have
How do I use list_jobs with the JOIN MCP? +
You call list_jobs to pull all open job titles and IDs in your account. This is the starting point when you need an overview of your current hiring needs.
What's the difference between get_candidate and list_candidates? +
list_candidates gives you a roster—a summary of everyone. You must use get_candidate to pull all the deep, specific details for one person only.
Can I find out which departments exist using list_departments? +
Yes. list_departments provides a clean list of every functional area (like HR or Sales) you can use to filter jobs or users later on.
How does get_application help with pipeline management? +
get_application pulls the granular data for one job submission, including form answers and notes. This is key for seeing exactly where a candidate stalled out in the process.
How do I check my connection status and permissions using the get_me tool? +
Calling get_me confirms your authentication and retrieves details about the connected account. This is a quick, reliable way to validate account access before running complex data pulls like listing all users or jobs.
What specific information does the get_job tool provide beyond just the job title? +
The get_job tool retrieves detailed descriptions, required skills, and internal metadata for a single role. Use this when your agent needs to analyze the full requirements of a posting rather than just viewing the list of open positions.
If I need a summary view of all recent applicants, should I use list_applications? +
Yes, list_applications gives you candidate summaries and basic application info across multiple roles. This is ideal for monitoring overall applicant flow or identifying new leads quickly, which differs from getting deep details on one specific record.
How can I find all possible job sites within the system using list_locations? +
Running list_locations retrieves a complete roster of every location where jobs are posted. Use this when you need to audit recruiting coverage or filter roles based on availability in a specific region.
How do I get JOIN API credentials? +
Log in to your JOIN account, navigate to User Settings > API Credentials, and generate a new token.
Can I see candidates for specific jobs? +
Yes, you can retrieve applications and candidates associated with your job postings using this MCP.
Does it support departments and locations? +
Yes, you can list all configured departments and office locations using the corresponding tools.
We've already built the connector for JOIN. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.