check_google_workspace — TamingDNS MCP Tool Read-only
check_google_workspace
(check google workspace) is one of 19 tools on the
TamingDNS
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_google_workspace from your client
- Claude Code TamingDNS check_google_workspace run in your project directory
- Claude Desktop TamingDNS check_google_workspace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TamingDNS check_google_workspace ~/.cursor/mcp.json
- VS Code TamingDNS check_google_workspace .vscode/mcp.json
- Zed TamingDNS check_google_workspace ~/.config/zed/settings.json
- Windsurf TamingDNS check_google_workspace ~/.codeium/windsurf/mcp_config.json
- Cline TamingDNS check_google_workspace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TamingDNS check_google_workspace ~/.gemini/settings.json
- Grok TamingDNS check_google_workspace .mcp.json (in your project root)
- ChatGPT TamingDNS check_google_workspace Settings → Connectors → Advanced → Developer mode
- Claude.ai TamingDNS check_google_workspace Settings → Connectors → Add custom connector
- LangChain TamingDNS check_google_workspace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://tamingdns.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.