Jibble MCP Server for CrewAI 10 tools — connect in under 2 minutes
Connect your CrewAI agents to Jibble through Vinkius, pass the Edge URL in the `mcps` parameter and every Jibble 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="Jibble Specialist",
goal="Help users interact with Jibble effectively",
backstory=(
"You are an expert at leveraging Jibble 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 Jibble "
"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)
* 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 Jibble MCP Server
Empower your AI agents with Jibble's time tracking and attendance platform. This MCP server allows you to list time entries, retrieve person details, track activities and projects, and view organization information directly through the Jibble API. Ideal for automating workforce management and productivity analysis.
When paired with CrewAI, Jibble becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Jibble tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
The Jibble 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 Jibble to CrewAI via MCP
Follow these steps to integrate the Jibble 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 Jibble
Why Use CrewAI with the Jibble MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Jibble 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
Jibble + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Jibble MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Jibble 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 Jibble, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Jibble 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 Jibble against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Jibble MCP Tools for CrewAI (10)
These 10 tools become available when you connect Jibble to CrewAI via MCP:
get_organization
Use to verify account-wide configuration. Retrieves organization details
get_person
Essential for detailed HR analysis of an individual team member. Retrieves details for a specific person
get_time_entry
Returns location data, activity notes, and associated device info. Use for auditing or correcting a specific employee time log. Retrieves details for a specific time entry
list_activities
g., "Meeting", "Development", "Break") that employees can select when clocking in. Useful for identifying high-level task categories. Lists all configured activities
list_clients
Useful for professional services tracking and billable hours auditing. Lists all configured clients
list_groups
g., "Sales Team", "Remote Workers") used to organize the workforce. Useful for group-based performance reporting. Lists all configured groups
list_locations
Useful for auditing site-based workforce distribution. Lists all configured locations
list_people
Includes names, emails, and internal IDs. Use this to identify personnel before querying their time entries. Lists all people in the organization
list_projects
Use this when the user asks for a project-based time breakdown. Lists all configured projects
list_time_entries
Returns employee IDs, entry times, and durations. Use this to monitor workforce activity and total work hours. Lists all time entries
Example Prompts for Jibble in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Jibble immediately.
"List all people in my Jibble organization."
"Show me the recent time entries."
"What are the active projects in Jibble?"
Troubleshooting Jibble MCP Server with CrewAI
Common issues when connecting Jibble 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
Jibble + CrewAI FAQ
Common questions about integrating Jibble 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 Jibble 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 Jibble to CrewAI
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.