MCP Calendar Tool Server

@KyanBergeron4Runr

Repository

Basic information

About MCP Calendar Tool Server

No overview available yet

MCP Calendar Tool Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

MCP Calendar Tool Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Calendar Tool Server?

A FastAPI-based MCP (Model Context Protocol) server that provides calendar management tools—check availability, add, update, and delete events—for AI agents running in n8n.

How to use MCP Calendar Tool Server?

Clone the repository, install dependencies with pip install -r requirements.txt, create a .env file with your API key, then run uvicorn main:app --host 0.0.0.0 --port 5000. Connect n8n’s MCP Client node to the SSE endpoint at http://localhost:8000/mcp-events.

Key features of MCP Calendar Tool Server

Server-Sent Events (SSE) for real-time tool discovery
HTTP endpoints for tool execution
Four calendar management tools: check availability, add, update, delete
API key authentication
Mock implementations ready for real calendar API integration
Structured project with Pydantic schemas and separate tool modules

Use cases of MCP Calendar Tool Server

AI agents in n8n that need to check room availability before scheduling meetings
Automating event creation from chatbot conversations or workflow triggers
Updating or rescheduling calendar events without manual intervention
Deleting cancelled events through automated n8n workflows

Frequently asked questions

What dependencies are required?

Python packages listed in `requirements.txt`; install with `pip install -r requirements.txt`.

How is authentication handled?

The server uses an API key set in the `.env` file as `API_KEY`. All tool execution requests require the `X-API-Key` header.

Does it integrate with real calendar services?

No, the current version uses mock implementations. Future improvements include integration with Google Calendar, Cal.com, and others.

What transport does the server use?

It uses Server-Sent Events (SSE) for tool discovery (`GET /mcp-events`) and HTTP POST for tool execution (`POST /mcp/message`).

What are the current limitations?

The server provides mock data only, no real calendar backend. It requires Python 3 and a running FastAPI instance.

Comments

More Productivity MCP servers

Phasio

Phasio is the operating platform contract manufacturers run on: quoting, production, and back office across additive, CNC, molding, and every process in between. This connector gives LLMs like Claude, ChatGPT and Grok ac

Etincel

AIStoryHub

Find the AI tells in your prose. Deterministic, local, runs in CI. MCP server + CLI + Action.

Vokolla Press Release Agent

Vokolla

Bring Vokolla’s all-in-one press release workflow into your AI conversation. Draft and refine English or Chinese releases with AI, compare distribution packages, save account drafts and track release progress and publica

RADAAR

Official repository bringing RADAAR's social media and content management tools to AI agents like Cursor, VS Code, and ChatGPT. Built on the agent-plugins.org standard, it connects seamlessly to the MCP server. Schedule

crosscode-cli

amsultan2010

Multiplayer coding in the agentic era through an MCP server for real-time codebase sync between your agents.