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.

Join MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Join
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Join through Vinkius, pass the Edge URL in the `mcps` parameter and every Join tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Join Specialist",
    goal="Help users interact with Join effectively",
    backstory=(
        "You are an expert at leveraging Join tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Join "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Join MCP Server

Empower your AI agents with JOIN's modern recruiting platform. This MCP server allows you to list job openings, retrieve candidate details, manage applications, and view organization departments directly through the JOIN API. Ideal for automating hiring workflows and talent acquisition.

When paired with CrewAI, Join becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Join tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

The Join MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Join to CrewAI via MCP

Follow these steps to integrate the Join MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Join

Why Use CrewAI with the Join MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Join through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Join + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Join MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Join for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Join, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Join tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Join against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Join MCP Tools for CrewAI (10)

These 10 tools become available when you connect Join to CrewAI via MCP:

get_application

Returns answers to form questions, internal notes, and application status. Use when evaluating a specific applicant or moving them through the pipeline. Retrieves details for a specific application

get_candidate

Use this for detailed candidate vetting and interview preparation. Retrieves details for a specific candidate

get_job

Returns descriptions, requirements, and internal metadata. Use this when the user needs to analyze the specifics of a particular role or prepare content related to it. Retrieves details for a specific job

get_me

Use this to verify identity and check connection health. Gets details about your own authenticated user

list_applications

Includes candidate summaries and basic application info. Essential for monitoring recent applicant flow and identifying new leads in the recruitment process. Lists all job applications

list_candidates

Returns candidate profiles, contact info, and their association with jobs. Use this when the user wants to search for specific people or perform bulk talent management tasks. Lists all candidates in the system

list_departments

g., Engineering, Sales, HR). Useful for filtering jobs or organizing the recruiting workspace by functional areas. Lists all organization departments

list_jobs

Returns job titles, IDs, and current status. Use this as the primary entry point to identify specific jobs or to provide an overview of the current hiring pipeline. Lists all job postings in JOIN

list_locations

Use this when the user asks for jobs in specific regions or needs to audit location-based recruiting data. Lists all job locations

list_users

Useful for identifying hiring managers or checking account access permissions. Lists all users in your JOIN account

Example Prompts for Join in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Join immediately.

"List all active job postings in JOIN."

"Show me the latest candidate applications."

"Get details for candidate ID '123'."

Troubleshooting Join MCP Server with CrewAI

Common issues when connecting Join to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Join + CrewAI FAQ

Common questions about integrating Join MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.