playwright-url-ok — Language vi MCP Tool
playwright-url-ok
(playwright url ok) is one of 31 tools on the
Language vi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call playwright-url-ok from your client
- Claude Code Language vi playwright-url-ok run in your project directory
- Claude Desktop Language vi playwright-url-ok ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Language vi playwright-url-ok ~/.cursor/mcp.json
- VS Code Language vi playwright-url-ok .vscode/mcp.json
- Zed Language vi playwright-url-ok ~/.config/zed/settings.json
- Windsurf Language vi playwright-url-ok ~/.codeium/windsurf/mcp_config.json
- Cline Language vi playwright-url-ok ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Language vi playwright-url-ok ~/.gemini/settings.json
- Grok Language vi playwright-url-ok .mcp.json (in your project root)
- ChatGPT Language vi playwright-url-ok Settings → Connectors → Advanced → Developer mode
- Claude.ai Language vi playwright-url-ok Settings → Connectors → Add custom connector
- LangChain Language vi playwright-url-ok pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lang-vi https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/lang-vi/mcp
Other tools on this server
- lang-vi
- utc-time
- timezone
- validate-json
- normalize-url
- inspect-robots
- domain-shape
- citation
- compatibility
- status-catalog
- iana-zones
- web-fetch
- fetch-status
- github-repo-shape
- weather-hint
- memory-key-count
- file-path-ok
- browser-url-ok
- think-steps
- search-query-len
- hn-front-count
- lib-docs-hint
- figma-url-shape
- jira-key-shape
- geo-hint
- calc-eval
- wiki-title-ok
- agent-tool-index
- people-search-index
- agent-ads-index
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.