{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-danielpeter-99-calcom-mcp","slug":"danielpeter-99-calcom-mcp","name":"Danielpeter-99/calcom-mcp","type":"mcp","url":"https://github.com/Danielpeter-99/calcom-mcp","page_url":"https://unfragile.ai/danielpeter-99-calcom-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-danielpeter-99-calcom-mcp__cap_0","uri":"capability://tool.use.integration.cal.com.event.type.schema.introspection.and.management","name":"cal.com event type schema introspection and management","description":"Exposes Cal.com event types as queryable MCP resources with full schema introspection, allowing LLMs to discover available scheduling templates, duration constraints, and booking rules without manual API documentation lookup. Implements resource-based MCP protocol binding to Cal.com's event type endpoints, enabling dynamic capability discovery at runtime.","intents":["Discover what event types are available in a Cal.com account without leaving the LLM context","Retrieve event type metadata (duration, availability rules, custom fields) to inform booking decisions","Build LLM agents that adapt booking logic based on available event types"],"best_for":["LLM agents managing scheduling workflows","Teams building Cal.com-integrated assistants","Developers automating event type discovery in multi-tenant scheduling systems"],"limitations":["Read-only introspection — does not support creating or modifying event types via MCP","Schema discovery latency depends on Cal.com API response time (typically 200-500ms per request)","No caching layer — each schema query hits the Cal.com API directly"],"requires":["Cal.com API key with event type read permissions","MCP client compatible with resource-based protocol (Claude, custom LLM agents)","Network connectivity to Cal.com API endpoints"],"input_types":["event type ID (string)","query filters (optional)"],"output_types":["JSON schema with event type metadata","structured availability rules","custom field definitions"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-danielpeter-99-calcom-mcp__cap_1","uri":"capability://tool.use.integration.booking.creation.with.availability.validation","name":"booking creation with availability validation","description":"Implements MCP tool for creating Cal.com bookings with real-time availability checking, guest email validation, and conflict detection against existing calendar entries. Translates LLM booking requests into Cal.com API calls with automatic timezone handling and slot validation before submission.","intents":["Create a booking for a specific time slot after confirming availability","Validate that a requested time slot is actually free before attempting to book","Handle timezone conversion for guests in different regions"],"best_for":["Conversational scheduling assistants","Automated meeting coordination agents","Multi-timezone booking workflows"],"limitations":["No support for recurring bookings or series creation","Timezone conversion relies on guest-provided timezone string — no automatic detection","Availability validation is point-in-time; race conditions possible in high-concurrency scenarios","Custom booking fields must be pre-defined in Cal.com event type; dynamic field creation not supported"],"requires":["Cal.com API key with booking creation permissions","Valid event type ID in Cal.com account","Guest email address for booking confirmation"],"input_types":["event type ID (string)","start time (ISO 8601 datetime)","guest email (string)","guest name (string)","custom fields (optional JSON object)"],"output_types":["booking confirmation object with booking ID","calendar event details","confirmation email status"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-danielpeter-99-calcom-mcp__cap_2","uri":"capability://tool.use.integration.scheduling.data.retrieval.and.filtering","name":"scheduling data retrieval and filtering","description":"Exposes MCP tools for querying Cal.com bookings, availability slots, and calendar data with filtering by date range, event type, and guest. Implements pagination and result limiting to handle large datasets efficiently, translating LLM filter requests into Cal.com API query parameters.","intents":["Retrieve all bookings for a specific date range to answer scheduling questions","Find available time slots for a given event type and date","Look up booking details by guest email or booking ID"],"best_for":["Scheduling analytics and reporting agents","Booking lookup and modification workflows","Calendar availability checking in conversational interfaces"],"limitations":["No full-text search across booking notes or custom fields","Pagination requires manual offset/limit handling by LLM — no cursor-based iteration","Date range queries limited to 90 days in Cal.com API (varies by plan)","Filtering by custom fields requires knowledge of exact field names and values"],"requires":["Cal.com API key with read permissions for bookings and availability","Event type ID for availability queries","Valid date range in ISO 8601 format"],"input_types":["date range (start/end ISO 8601)","event type ID (optional)","guest email filter (optional)","pagination parameters (limit, offset)"],"output_types":["array of booking objects","array of available time slots","booking metadata (duration, guest count, custom fields)"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-danielpeter-99-calcom-mcp__cap_3","uri":"capability://tool.use.integration.mcp.protocol.server.implementation.for.cal.com","name":"mcp protocol server implementation for cal.com","description":"Implements a complete MCP server that exposes Cal.com scheduling capabilities as standardized MCP resources and tools, enabling any MCP-compatible LLM client (Claude, custom agents) to interact with Cal.com without custom integration code. Handles MCP protocol handshake, resource discovery, and tool invocation routing.","intents":["Connect Claude or other MCP clients to Cal.com without building custom API wrappers","Enable LLM agents to discover available Cal.com operations through MCP resource/tool listing","Standardize Cal.com integration across multiple LLM applications"],"best_for":["Teams deploying Claude with Cal.com scheduling","Developers building multi-LLM scheduling agents","Organizations standardizing on MCP for tool integration"],"limitations":["MCP protocol overhead adds ~50-100ms latency per tool invocation vs direct API calls","Requires MCP-compatible LLM client — not compatible with standard REST API consumers","No built-in request rate limiting or quota management — relies on Cal.com API limits","Error handling and retry logic must be implemented at the MCP server level"],"requires":["MCP client library (Claude SDK, custom MCP client)","Node.js runtime for MCP server execution","Cal.com API key with appropriate permissions"],"input_types":["MCP protocol messages (JSON-RPC 2.0)","resource requests","tool invocation payloads"],"output_types":["MCP protocol responses","resource listings","tool execution results"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-danielpeter-99-calcom-mcp__cap_4","uri":"capability://tool.use.integration.guest.information.capture.and.custom.field.mapping","name":"guest information capture and custom field mapping","description":"Supports capturing guest details (name, email, phone, custom fields) during booking creation and maps them to Cal.com event type custom field definitions. Validates field types and required constraints before submission, enabling LLMs to collect structured guest information without manual field validation.","intents":["Collect guest phone number or company name during booking if event type requires it","Map conversational input to Cal.com custom field definitions automatically","Validate guest information against event type constraints before booking"],"best_for":["Conversational booking assistants with custom data collection","Multi-field booking forms driven by LLMs","Workflows requiring guest qualification or intake information"],"limitations":["Custom field validation limited to type checking — no regex or complex validation rules","No support for conditional fields (e.g., show phone only if guest is external)","Field mapping requires exact match of field names between LLM context and Cal.com definition","No file upload support for custom fields"],"requires":["Cal.com event type with custom fields pre-configured","Knowledge of custom field names and types in target event type","Guest information in structured format (JSON object)"],"input_types":["guest name (string)","guest email (string)","guest phone (optional string)","custom fields (JSON object with field names as keys)"],"output_types":["validated guest object","field validation errors (if any)","booking payload with guest details"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-danielpeter-99-calcom-mcp__cap_5","uri":"capability://safety.moderation.cal.com.api.authentication.and.credential.management","name":"cal.com api authentication and credential management","description":"Handles Cal.com API key storage, validation, and credential injection into all MCP tool invocations. Implements secure credential handling patterns to prevent API key exposure in logs or LLM context, with support for multiple Cal.com accounts via environment variable or configuration file.","intents":["Securely authenticate to Cal.com API without exposing credentials in LLM prompts","Support multiple Cal.com accounts in a single MCP server instance","Validate API key permissions before executing booking or modification operations"],"best_for":["Production deployments of Cal.com MCP servers","Multi-tenant scheduling systems","Teams requiring credential isolation between environments"],"limitations":["No built-in credential rotation — requires manual API key updates","API key validation is best-effort (tests basic connectivity, not full permission scope)","No support for OAuth 2.0 or token-based authentication — API key only","Credentials stored in environment variables or config files — no secure vault integration"],"requires":["Cal.com API key (generated in Cal.com account settings)","Environment variable or configuration file for credential storage","Node.js process with access to environment variables"],"input_types":["API key (string)","Cal.com account identifier (optional)"],"output_types":["authentication status (success/failure)","credential validation result"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-danielpeter-99-calcom-mcp__cap_6","uri":"capability://safety.moderation.error.handling.and.api.failure.recovery","name":"error handling and api failure recovery","description":"Implements MCP-level error handling for Cal.com API failures, translating HTTP errors and Cal.com-specific error codes into structured MCP error responses. Includes retry logic for transient failures (rate limits, timeouts) and provides detailed error messages to LLMs for decision-making.","intents":["Handle Cal.com API rate limiting gracefully without failing the entire booking workflow","Provide LLMs with actionable error messages when bookings fail","Retry transient failures automatically without LLM intervention"],"best_for":["Production scheduling agents requiring reliability","High-volume booking workflows with rate limit concerns","Conversational interfaces needing user-friendly error messages"],"limitations":["Retry logic uses exponential backoff with fixed max attempts — no adaptive retry strategy","Rate limit detection relies on HTTP 429 status code — Cal.com-specific rate limit headers not parsed","No circuit breaker pattern — repeated failures don't trigger fallback behavior","Error messages are Cal.com API responses — may not be user-friendly for end users"],"requires":["Cal.com API key with appropriate permissions","Network connectivity to Cal.com API","MCP client capable of handling structured error responses"],"input_types":["Cal.com API response (HTTP status, error body)"],"output_types":["MCP error response with error code and message","retry indication (if applicable)","fallback suggestions (optional)"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"high","permissions":["Cal.com API key with event type read permissions","MCP client compatible with resource-based protocol (Claude, custom LLM agents)","Network connectivity to Cal.com API endpoints","Cal.com API key with booking creation permissions","Valid event type ID in Cal.com account","Guest email address for booking confirmation","Cal.com API key with read permissions for bookings and availability","Event type ID for availability queries","Valid date range in ISO 8601 format","MCP client library (Claude SDK, custom MCP client)"],"failure_modes":["Read-only introspection — does not support creating or modifying event types via MCP","Schema discovery latency depends on Cal.com API response time (typically 200-500ms per request)","No caching layer — each schema query hits the Cal.com API directly","No support for recurring bookings or series creation","Timezone conversion relies on guest-provided timezone string — no automatic detection","Availability validation is point-in-time; race conditions possible in high-concurrency scenarios","Custom booking fields must be pre-defined in Cal.com event type; dynamic field creation not supported","No full-text search across booking notes or custom fields","Pagination requires manual offset/limit handling by LLM — no cursor-based iteration","Date range queries limited to 90 days in Cal.com API (varies by plan)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.39,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.037Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=danielpeter-99-calcom-mcp","compare_url":"https://unfragile.ai/compare?artifact=danielpeter-99-calcom-mcp"}},"signature":"q5drOUwxMTv3pNpLkUCVAiqUC64Uj49+Yo4lPoUev9R0lNNqPLzKxUyWYDQF5nsEvw6HnJNJUXEV49aiNEUaAg==","signedAt":"2026-06-21T07:43:35.737Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/danielpeter-99-calcom-mcp","artifact":"https://unfragile.ai/danielpeter-99-calcom-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=danielpeter-99-calcom-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}