by Google Calendar
MCP server for Google Calendar — enables Claude to interact with Google Calendar data and workflows.
Google Calendar MCP server for Claude integration. Enables AI assistants to interact with Google Calendar data and workflows.
Google Calendar is an official MCP server included in Anthropic's knowledge-work-plugins repository. It enables Claude to interact with Google Calendar through the Model Context Protocol. Protocol: HTTP. Endpoint: configured per environment. Used in plugins: customer-support, design, engineering, enterprise-search, finance, human-resources, legal, marketing, operations, product-management, productivity, sales, small-business.
Add the following to your .mcp.json file to connect Claude to Google Calendar. No local installation required — this is a remote HTTP server.
Proprietary
Google Calendar is a proprietary service. Usage is subject to Google Calendar's terms of service.
README content is unavailable from source data for this server.
Open GitHub repository →Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
We evaluated Google Calendar against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Google Calendar is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, Google Calendar benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Strong directory entry: Google Calendar surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired Google Calendar into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, Google Calendar benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
I recommend Google Calendar for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Google Calendar is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Google Calendar has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: Google Calendar is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 35
Slack
MCP server for Slack — enables Claude to interact with Slack data and workflows.
★ —
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.