parky_get_waits — Parky — Park Planning MCP Tool
parky_get_waits
(parky get waits) is one of 8 tools on the
Parky — Park Planning
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call parky_get_waits from your client
- Claude Code Parky — Park Planning parky_get_waits run in your project directory
- Claude Desktop Parky — Park Planning parky_get_waits ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Parky — Park Planning parky_get_waits ~/.cursor/mcp.json
- VS Code Parky — Park Planning parky_get_waits .vscode/mcp.json
- Zed Parky — Park Planning parky_get_waits ~/.config/zed/settings.json
- Windsurf Parky — Park Planning parky_get_waits ~/.codeium/windsurf/mcp_config.json
- Cline Parky — Park Planning parky_get_waits ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Parky — Park Planning parky_get_waits ~/.gemini/settings.json
- Grok Parky — Park Planning parky_get_waits .mcp.json (in your project root)
- ChatGPT Parky — Park Planning parky_get_waits Settings → Connectors → Advanced → Developer mode
- Claude.ai Parky — Park Planning parky_get_waits Settings → Connectors → Add custom connector
- LangChain Parky — Park Planning parky_get_waits pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http parky https://mcp.parkypass.com/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 4 October 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.