How to Use the Cronofy MCP in LangChain

Q: Can LangChain agents manage existing events in Cronofy?

Yes. Your agent can use readevents to find a meeting's ID, then pass that ID to deleteevent. This is useful for building chains that clean up or modify scheduled events based on new information.

Q: What's the best way to handle multiple calendars with Cronofy and LangChain?

Use the listcalendars tool first. This gives your agent a list of available calendars, which it can use as context for all subsequent actions. Your chain can then be designed to check for availability across specific calendars.

Build calendar-aware agent chains that find availability and book meetings using Cronofy and LangChain.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cronofy MCP to LangChain

Create your Vinkius account to connect Cronofy to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Cronofy with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Chain together scheduling actions

Your LangChain agent can now manage calendars. It can use `query_availability` to find an open slot, then immediately follow up with `create_event` to book the meeting. This isn't just a single tool call—it's a sequence your agent reasons through. This is what ReAct agents were built for. You give the agent a goal, like "book a 30-minute meeting with Dave next week," and it figures out the necessary steps. It checks for free time, handles the booking, and confirms the result, all in one chain.

Manage events with multi-step logic

This isn't just for creating events. Your agents can build logic to manage existing ones. Use `read_events` to find a specific meeting, then give your agent rules for when to use `delete_event`. You can design chains that find all meetings matching a certain criteria, ask for confirmation, and then clear them from the calendar. LangSmith gives you full visibility into each step, so you can see exactly what your agent saw and why it made its decision.

Build context-aware LangChain agents

An agent needs context to do its job properly. Before it starts booking meetings, it can use `get_user_info` and `list_calendars` to understand whose calendars it's managing and what permissions it has. This lets you build more reliable agents. They won't just blindly execute commands. They'll check the account setup first, ensuring they're acting on the right calendar and have the right access. This Cronofy MCP Server provides all the necessary tools for that initial check.

Setup guide

Set up Cronofy MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes Cronofy tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "cronofy-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent Cronofy transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cronofy. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Cronofy now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Cronofy MCP in LangChain

You pass the Cronofy tools to your agent. The agent will automatically chain tools like `query_availability` and `create_event` to accomplish the goal. You don't manage the individual calls; the agent's reasoning engine does.

Yes. Your agent can use `read_events` to find a meeting's ID, then pass that ID to `delete_event`. This is useful for building chains that clean up or modify scheduled events based on new information.

Use the `list_calendars` tool first. This gives your agent a list of available calendars, which it can use as context for all subsequent actions. Your chain can then be designed to check for availability across specific calendars.

LangSmith gives you a complete trace of the agent's execution. You can see every Cronofy tool call, the exact data passed to `create_event`, and the result that came back. It makes debugging complex chains much easier.

This server only processes the calendar event and user account data needed for scheduling. Vinkius runs each tool call in an isolated sandbox that's destroyed after execution. Your calendar data is only in memory for the duration of the API call.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript