What Calfeed MCP server does
Calfeed MCP server converts a written schedule into a live calendar link. That link is intended for people who want to subscribe to the schedule through Apple Calendar, Google Calendar, or Outlook. The available description focuses on publishing a schedule from text rather than managing an existing calendar account.
This makes the service relevant when a schedule begins as prose or another written representation and needs to become a calendar subscription. The result is a link that can be shared with the people who need to follow the schedule. The provided material does not describe whether the service creates individual events, recurring events, reminders, or other calendar metadata, so those details should not be assumed.
Tools and capabilities
The documented capability is schedule conversion and publication:
- Accepts a written schedule as the source material.
- Produces a live calendar link.
- Supports subscription by users of Apple Calendar, Google Calendar, and Outlook.
No separate tool names, parameters, response formats, or API operations are documented in the supplied material. If an agent needs to edit an existing calendar, invite attendees, inspect availability, or perform another calendar operation, the listing does not establish that Calfeed supports it.
The Calfeed MCP server is therefore best evaluated as a focused publishing path for schedules. It may fit workflows where an agent receives schedule text and needs to make that schedule available through common calendar applications. It is less clearly suited to workflows that require full calendar administration, because no such functions are described.
Limitations and notes
The repository README is unavailable, so the supplied information does not specify installation steps, transport, authentication, environment variables, input schema, output schema, update behavior, or error handling. It also does not identify named MCP client applications or provide a license. Those details should be confirmed from the service documentation before implementation.
The description says the link is live, but it does not explain how changes to the written schedule are made, how quickly subscribers see updates, whether links are public or private, or how access is controlled. It also does not state whether a schedule can be removed or whether multiple schedules can be managed independently.
Use the Calfeed MCP server when the known requirement is to turn written schedule content into a subscribable calendar link. Treat any broader calendar features, client compatibility beyond the three named calendar products, or operational guarantees as unverified until documented.