Alfred

What alfred_ MCP server does

The alfred_ MCP server connects an MCP-enabled AI agent with Gmail, Outlook, and calendars. Its stated purpose is to let an agent work with real communication and scheduling data rather than only producing text about what a user could do.

The available description groups its work into five actions: reading, drafting, sending, scheduling, and organizing. These actions cover both message workflows and calendar-related tasks. Reading can support retrieving relevant information, while drafting and sending address different stages of email work. Scheduling applies to calendar activity, and organizing describes arranging or managing information within the connected services.

The material does not identify whether Gmail and Outlook are both available for every action, so the exact operation-to-service mapping should be confirmed before deployment.

Tools and capabilities

The listed capabilities are:

• Read information from connected Gmail, Outlook, and calendar services.
• Create email drafts for review or later action.
• Send messages through the connected communication services.
• Schedule calendar items.
• Organize email or calendar information.

These capabilities make the alfred_ MCP server relevant to agents that need to retrieve communication context, prepare outgoing email, complete sending workflows, or coordinate calendar activity. The provided material does not name individual MCP tool names, parameters, return formats, supported calendar providers, or rules for confirmation before sending or scheduling.

Limitations and notes

The supplied material contains no README or setup documentation. As a result, it does not establish installation commands, authentication steps, required environment variables, transport options, supported MCP clients, permission scopes, or operational limits. Those details should be checked at the service source before implementation.

The alfred_ MCP server is described at the capability level only. The description confirms connections to Gmail, Outlook, and calendars, but does not document whether those connections are configured independently, how accounts are selected, or how conflicts between services are handled. It also does not explain how organizing actions work or whether sending and scheduling require user approval.

For evaluation, verify the service's account-access model and the exact behavior of write operations before granting it access to production mailboxes or calendars. The available information supports treating the alfred_ MCP server as a communication and calendar interface, but not assuming any particular installation or security model.