Skip to main content
Glama
shadowfax92

MCP Apple Calendars

by shadowfax92

createCalendarEvent

Add events to Apple Calendar on macOS by specifying title, dates, calendar, and optional details like location and notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdYes
titleYes
startDateYes
endDateYes
locationNo
notesNo

Implementation Reference

  • Core handler function that formats dates and creates the calendar event via POST to the API bridge endpoint.
    export async function createCalendarEvent(
      calendarId: string, 
      title: string, 
      startDate: string, 
      endDate: string, 
      location?: string, 
      notes?: string
    ): Promise<any> {
      try {
        // Format dates using our flexible date formatter
        const formattedStartDate = formatDate(startDate);
        const formattedEndDate = formatDate(endDate);
        
        if (!formattedStartDate || !formattedEndDate) {
          throw new Error('Invalid date format provided. Please use one of the supported formats.');
        }
        
        // Create the event data
        const eventData: any = {
          title,
          startDate: formattedStartDate,
          endDate: formattedEndDate
        };
        
        // Add optional fields if provided
        if (location) eventData.location = location;
        if (notes) eventData.notes = notes;
        
        
        // Send the request
        const response = await axios.post(
          `${API_BASE_URL}/calendars/${calendarId}/events`, 
          eventData
        );
        
        return response.data;
      } catch (error) {
        console.error(`Failed to create event "${title}" in calendar "${calendarId}":`, error);
        throw new Error(`Failed to create calendar event: ${error}`);
      }
    }
  • Zod validation schema defining the input parameters for the createCalendarEvent tool.
    { 
      calendarId: z.string(),
      title: z.string(),
      startDate: z.string(),
      endDate: z.string(),
      location: z.string().optional(),
      notes: z.string().optional()
    },
  • src/index.ts:97-160 (registration)
    Registers the createCalendarEvent tool with the MCP server, providing name, input schema, and handler function.
    server.tool(
      "createCalendarEvent",
      { 
        calendarId: z.string(),
        title: z.string(),
        startDate: z.string(),
        endDate: z.string(),
        location: z.string().optional(),
        notes: z.string().optional()
      },
      async ({ calendarId, title, startDate, endDate, location, notes }) => {
        try {
          try {
            const result = await calendars.createCalendarEvent(
              calendarId, 
              title, 
              startDate, 
              endDate, 
              location, 
              notes
            );
            
            return {
              content: [{ 
                type: "text", 
                text: JSON.stringify({ 
                  success: true, 
                  message: "Event created", 
                  event: result 
                }) 
              }]
            };
          } catch (error: any) {
            // Check if it's a date format error
            if (error.message && (error.message.includes('date') || 
                (error.response?.data?.reason && error.response.data.reason.includes('ISO8601')))) {
              return {
                content: [{ 
                  type: "text", 
                  text: JSON.stringify({ 
                    error: "Failed to create event due to date format issues", 
                    message: "The Calendar API requires a specific ISO8601 format that we couldn't determine. The Swift API is expecting a specific format that we haven't been able to match.",
                    details: "This is a known issue with the Calendar API Bridge. Please check the API documentation for the correct date format.",
                    workaround: "You can try creating events directly through the macOS Calendar app instead."
                  }) 
                }],
                isError: true
              };
            }
            
            // If it's not a date format error, rethrow
            throw error;
          }
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ error: "Failed to create event" }) 
            }],
            isError: true
          };
        }
      }
    );
  • Thin MCP-specific handler wrapper that invokes the core createCalendarEvent function and formats the response for MCP.
    async ({ calendarId, title, startDate, endDate, location, notes }) => {
      try {
        try {
          const result = await calendars.createCalendarEvent(
            calendarId, 
            title, 
            startDate, 
            endDate, 
            location, 
            notes
          );
          
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ 
                success: true, 
                message: "Event created", 
                event: result 
              }) 
            }]
          };
        } catch (error: any) {
          // Check if it's a date format error
          if (error.message && (error.message.includes('date') || 
              (error.response?.data?.reason && error.response.data.reason.includes('ISO8601')))) {
            return {
              content: [{ 
                type: "text", 
                text: JSON.stringify({ 
                  error: "Failed to create event due to date format issues", 
                  message: "The Calendar API requires a specific ISO8601 format that we couldn't determine. The Swift API is expecting a specific format that we haven't been able to match.",
                  details: "This is a known issue with the Calendar API Bridge. Please check the API documentation for the correct date format.",
                  workaround: "You can try creating events directly through the macOS Calendar app instead."
                }) 
              }],
              isError: true
            };
          }
          
          // If it's not a date format error, rethrow
          throw error;
        }
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ error: "Failed to create event" }) 
          }],
          isError: true
        };
      }
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shadowfax92/apple-calendar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server