2,500+ MCP servers ready to use
Vinkius

Reclaim.ai MCP Server for CrewAI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Reclaim.ai through the Vinkius — pass the Edge URL in the `mcps` parameter and every Reclaim.ai 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="Reclaim.ai Specialist",
    goal="Help users interact with Reclaim.ai effectively",
    backstory=(
        "You are an expert at leveraging Reclaim.ai 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 Reclaim.ai "
        "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)
Reclaim.ai
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 Reclaim.ai MCP Server

Connect your Reclaim.ai intelligent scheduling assistant directly to your AI agent. Enabling this integration turns your AI into an advanced executive assistant, capable of instantly scanning your schedule, managing priorities, and inserting new smart tasks into your Google Calendar effortlessly.

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

What you can do

  • Smart Task Management — Create, update, or delete dynamic tasks, adjusting their duration and priority while letting Reclaim handle the automated calendar placement.
  • Habit Tracking — Review your recurring protected time blocks (Habits) scheduled to accommodate deep work, routines, and breaks.
  • Calendar Review — List both manual and AI-scheduled events for specific date ranges to understand your true availability.
  • Scheduling Links — Retrieve your shareable booking page URLs instantly to send to teammates or clients directly from chat.
  • Time Analytics — Extract quantitative data tracking how you allocate focus across categories over customized ranges.

The Reclaim.ai 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 Reclaim.ai to CrewAI via MCP

Follow these steps to integrate the Reclaim.ai 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 Reclaim.ai

Why Use CrewAI with the Reclaim.ai MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Reclaim.ai 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 the 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

Reclaim.ai + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries Reclaim.ai 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 Reclaim.ai, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Reclaim.ai 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 Reclaim.ai against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Reclaim.ai MCP Tools for CrewAI (10)

These 10 tools become available when you connect Reclaim.ai to CrewAI via MCP:

01

create_task

Specify title, duration in minutes, due date, and priority (P1 to P4). Creates a new task to be auto-scheduled by Reclaim.ai

02

delete_task

This action is irreversible. Deletes a task from Reclaim.ai

03

get_analytics

Retrieves time analytics for a specific date range

04

get_current_user

Retrieves the authenticated user profile

05

get_task

Retrieves details for a specific Reclaim.ai task

06

list_calendar_events

Lists all events on the Reclaim.ai planner for a date range

07

list_habits

Lists all habits configured in Reclaim.ai

08

list_scheduling_links

Lists all Reclaim.ai scheduling links

09

list_tasks

You can filter by status (NEW, SCHEDULED, IN_PROGRESS, COMPLETE). Lists all tasks managed by Reclaim.ai

10

update_task

Provide a JSON object with the updates. Updates an existing Reclaim.ai task

Example Prompts for Reclaim.ai in CrewAI

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

01

"Create a new task to draft the Q3 analytics report taking 3 hours with P1 priority."

02

"Delete task with ID 20392."

03

"Show my time spent analytics between 2024-01-01 and 2024-01-31."

Troubleshooting Reclaim.ai MCP Server with CrewAI

Common issues when connecting Reclaim.ai 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

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

Reclaim.ai + CrewAI FAQ

Common questions about integrating Reclaim.ai 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 Reclaim.ai to CrewAI

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