Calendar vs A11y Check — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Calendar vs A11y Check
In-depth architectural comparison of the Calendar and A11y Check MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Calendar
Workplace & Productivity · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
A11y Check
Browser Automation · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Calendar if you need specialized Workplace & Productivity tools running via a local process. Choose A11y Check if your workspace requires Browser Automation integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
C
Choose Calendar when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Read the .ics your calendar already exports: what is on this week, when you are actually free, what is double-booked, and turn a meeting into billable time. All local.
Check a web page for accessibility problems in a real browser, with the code that fixes each one.
Read a `.ics` file (`path`), pasted contents (`text`) or a public feed (`url`, Pro) and keep it locally under a name. Importing the same name again replaces it.
calendars_list
Every imported calendar: name, source, event count, size, when it was imported.
events_list
Every event between two dates with recurring series expanded to real occurrences, sorted, in your own time zone. Each row carries an id.
events_search
Events whose title, description, location, organizer or attendees contain a phrase.
free_busy
Merged busy blocks and the free gaps inside your working hours, day by day. Events marked free/transparent do not count as busy.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Calendar is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, A11y Check belongs to Browser Automation using remote streaming HTTP/SSE transport. Select Calendar when you need capabilities focused on workplace & productivity and A11y Check when you require tools for browser automation.
Every pair of events that overlap, with the overlap in minutes -- across all calendars, so a client call clashing with a school run is caught. A longer window is shortened to the free 31 days and answered, never refused.
next_event
The next thing that has not started, and how long until it does.
event_export
Write chosen events (by id, or a whole window) to a new `.ics` you can send. Times in UTC, so it lands correctly in any client.
event_to_time_entry
Turn one meeting into the exact arguments for the time-tracker's `entry_add`, so a call becomes billable time without retyping it.