Finch MCP Server for CrewAI 11 tools — connect in under 2 minutes
Connect your CrewAI agents to Finch through Vinkius, pass the Edge URL in the `mcps` parameter and every Finch tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Finch Specialist",
goal="Help users interact with Finch effectively",
backstory=(
"You are an expert at leveraging Finch 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 Finch "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 11 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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 Finch MCP Server
Finch is the unified API for HRIS and payroll. This MCP server allows your AI agent to interact with various HR and payroll providers through a single integration flawlessly.
When paired with CrewAI, Finch becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Finch tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
Key Features
- Directory Orchestration — List all employees in the connected organization and fetch detailed profiles natively.
- Employment Intelligence — Retrieve granular employment data including job titles, departments, and compensation flawlessly.
- Payroll Transparency — Access pay groups and individual pay statements to monitor payroll data synchronously.
- Connection Introspection — Check the status, provider, and authorized permissions for any connection flawlessly native.
- Automated Job Tracking — Monitor data sync jobs to ensure your HRIS data is always up to date flawlessly through the agent.
- Provider Discovery — List all supported HRIS and payroll providers to verify integration compatibility flawlessly.
The Finch MCP Server exposes 11 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 Finch to CrewAI via MCP
Follow these steps to integrate the Finch 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 11 tools from Finch
Why Use CrewAI with the Finch MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Finch 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
Finch + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Finch MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Finch 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 Finch, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Finch 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 Finch against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Finch MCP Tools for CrewAI (11)
These 11 tools become available when you connect Finch to CrewAI via MCP:
get_automated_job
Get details for a specific automated job
get_company
Get organization data (legal name, EIN, primary address)
get_employment
Get employment data for an individual (title, salary, department, etc.)
get_individual
Get personal data for an individual (name, email, SSN, etc.)
get_me
Get details for the authorized application/user connection
introspect
Check the status and permissions of the current connection
list_automated_jobs
List automated data sync jobs
list_directory
Read the employee directory for the connected organization
list_pay_groups
List pay groups for the organization
list_pay_statements
List pay statements for a specific payment ID
list_supported_providers
List all HRIS/Payroll providers supported by Finch
Example Prompts for Finch in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Finch immediately.
"List all employees in the directory."
"Check the status of my connection to Gusto."
"List pay statements for payment ID pmt_123."
Troubleshooting Finch MCP Server with CrewAI
Common issues when connecting Finch to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Finch + CrewAI FAQ
Common questions about integrating Finch MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Finch with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Finch to CrewAI
Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.