pulsemcp scanned Safe content atomic mcp-remote

Google Workspace Automation

This MCP server provides Google Workspace automation through Google Apps Script Web Apps, offering 23 tools for managing Gmail, Calendar, Drive, Docs, Sheets, Slides, and Forms programmatically. Built by Kanshi Tanaike using the MCPApp and ToolsForMCPServer libraries, it leverages Google Apps Script's built-in authorization to eliminate OAuth complexity while enabling AI assistants to perform complex multi-step workflows like searching emails, creating calendar events, generating presentations with Gemini API integration, building surveys and quizzes in Forms, and managing files across Google services. The implementation supports advanced operations like automated email drafting and sending, weather and currency data retrieval, and dynamic presentation generation, making it valuable for productivity automation, educational content creation, and building AI assistants that need seamless access to Google Workspace without manual authentication setup.

Cognium trust score

14%

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-19.

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

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: communication
Source: PulseMCP
Repository: github.com/tanaikech/toolsformcpserver
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Google Workspace Automation 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"