{
"mcpServers": {
"calendly-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Open source calendly mcp server
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 173 days ago. 11 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Calendly Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for integrating with the Calendly API. This server provides tools to interact with Calendly's scheduling platform, allowing you to retrieve user information, list events, manage invitees, cancel events, and schedule meetings directly via the new Scheduling API.
Run directly without installation:
npx calendly-mcp-server
git clone https://github.com/meAmitPatil/calendly-mcp-server.git
cd calendly-mcp-server
npm install
npm run build
This server supports two authentication methods:
For internal applications or personal use:
export CALENDLY_API_KEY="your_personal_access_token_here"
For public applications that multiple users will use:
export CALENDLY_CLIENT_ID="your_client_id_here"
export CALENDLY_CLIENT_SECRET="your_client_secret_here"
export CALENDLY_ACCESS_TOKEN="your_access_token_here"
export CALENDLY_REFRESH_TOKEN="your_refresh_token_here"
For better performance and automatic defaults, you can set user-specific URIs:
export CALENDLY_USER_URI="https://api.calendly.com/users/your_user_id"
export CALENDLY_ORGANIZATION_URI="https://api.calendly.com/organizations/your_org_id"
These can be obtained by running get_current_user after authentication. When set, the server will automatically use these as defaults for API calls that require user context.
Add the server to your MCP client configuration (e.g., Claude Desktop):
For Personal Access Token:
{
"mcpServers": {
"calendly": {
"command": "npx",
"args": ["calendly-mcp-server"],
"env": {
"CALENDLY_API_KEY": "your_personal_access_token_here",
"CALENDLY_USER_URI": "https://api.calendly.com/users/your_user_id",
"CALENDLY_ORGANIZATION_URI": "https://api.calendly.com/organizations/your_org_id"
}
}
}
}
For OAuth 2.0:
{
"mcpServers": {
"calendly": {
"command": "npx",
"args": ["calendly-mcp-server"],
"env": {
"CALENDLY_CLIENT_ID": "your_client_id_here",
"CALENDLY_CLIENT_SECRET": "your_client_secret_here",
"CALENDLY_ACCESS_TOKEN": "your_access_token_here",
"CALENDLY_REFRESH_TOKEN": "your_refresh_token_here",
"CALENDLY_USER_URI": "https://api.calendly.com/users/your_user_id",
"CALENDLY_ORGANIZATION_URI": "https://api.calendly.com/organizations/your_org_id"
}
}
}
}
... [View full README on GitHub](https://github.com/meAmitPatil/calendly-mcp-server#readme)