2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Picktime Specialist",
    goal="Help users interact with Picktime effectively",
    backstory=(
        "You are an expert at leveraging Picktime 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 Picktime "
        "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)
Picktime
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 Picktime MCP Server

Connect your Picktime organization account to your AI agent and turn complex scheduling and availability management into a simple chat conversation.

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

What you can do

  • Space & Resources — Easily retrieve structural logistics utilizing list_locations and inspect the service portfolio actively using list_services.
  • Staff Management — Gather team rosters through list_staff to orchestrate proper assignment mappings for upcoming reservations.
  • Booking Operations — Execute deep audits with list_bookings, review detailed entries (get_booking_details), and cleanly back out utilizing cancel_booking.
  • Availability Mapping — Audit live calendar empty spots using get_availability or check structured slots via list_classes for seamless planning.

The Picktime 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 Picktime to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

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

Why Use CrewAI with the Picktime MCP Server

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

01

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

02

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

03

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

04

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

Picktime + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Picktime MCP Tools for CrewAI (10)

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

01

cancel_booking

Cancel a Picktime booking with a reason. The customer receives a cancellation notification and the time slot becomes available again for new bookings

02

get_availability

Get available booking time slots for a specific Picktime service on a given date. Returns free windows considering staff schedules, existing bookings, and buffer times. Essential for building custom booking flows

03

get_booking_details

Get full details of a specific Picktime booking including customer contact info, service booked, staff assigned, start/end times, payment status, and any customer notes

04

get_location

Used to resolve workspace boundaries before hitting schedules. Get detailed configuration for a specific Picktime location by ID. Returns location name, address, timezone, working hours, booking URL, and linked calendar/payment integrations

05

get_service_details

Get detailed configuration for a specific Picktime service. Returns name, duration, price, description, staff assignments, booking limits, and cancellation policy

06

list_bookings

List all bookings for a Picktime location with optional date filter. Returns customer names, booked services, staff assignments, times, statuses, and payment info. Essential for schedule management

07

list_classes

List all group classes configured for a Picktime location. Classes are multi-attendee bookings with capacity limits — yoga sessions, workshops, group trainings

08

list_locations

List all business locations configured in Picktime. Each location operates independently with its own services, staff, working hours, and booking pages. Multi-location businesses manage branches separately

09

list_services

List all bookable services for a Picktime location. Returns service names, durations, prices, descriptions, assigned staff, and buffer times. Services define what customers can book

10

list_staff

List all staff members at a Picktime location. Returns staff names, emails, roles, assigned services, working hours, and active status. Staff availability determines bookable time slots

Example Prompts for Picktime in CrewAI

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

01

"Find all of our active clinic locations in the Picktime registry."

02

"Cancel the booking record identified as BK123456."

03

"Can you check the availability data for 'Hair Styling' next Monday?"

Troubleshooting Picktime MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Picktime + CrewAI FAQ

Common questions about integrating Picktime MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Picktime to CrewAI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.