pulsemcp scanned Safe content atomic mcp-remote

Google Calendar

The Google Calendar MCP server provides AI assistants with direct access to Google Calendar operations through a Python-based implementation. Built with FastAPI and the Google Calendar API, it enables calendar management (listing, creating), event operations (finding, creating, updating, deleting), and advanced scheduling features like free/busy queries and mutual availability scheduling. The server handles OAuth 2.0 authentication with token refresh, supports both HTTP endpoints and stdio-based MCP communication, and includes detailed logging. It's particularly valuable for users who need to manage their schedules, coordinate meetings, or analyze calendar usage patterns without leaving their AI assistant conversation context.

Cognium trust score

35%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: monitoring
Source: PulseMCP
Repository: github.com/deciduus/calendar-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Google Calendar from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"