ToolsMCP
Google Calendar MCP
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- renzojohnson.com
- Prerequisites
- Install @renzo.johnson/google-calendar-mcp from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 26.11.14 · updated
- Official links
Publisher’s description
Google Calendar MCP server: list, read, create, update and delete events and calendars.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 26.11.14, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- renzojohnson.com
- Version observed
- 26.11.14
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.renzojohnson%2Fgoogle-calendar-mcp/versions/26.11.14
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Manage calendar events from an assistant | Publisher description mentions “calendar”, “calendars”, “events”. | No connection check or task run. Capability is as described by the publisher. | Rule calendar-events matched: “calendar”, “calendars”, “events”. Rule calendar-events. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@renzo.johnson/google-calendar-mcp(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.renzojohnson/google-calendar-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.