Gachi Data API — Japa… vs Playwright MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Gachi Data API — Japan Station & Accessibility Data vs Playwright MCP
In-depth architectural comparison of the Gachi Data API — Japan Station & Accessibility Data and Playwright MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Gachi Data API — Japan Station & Accessibility Data
Browser Automation · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Playwright MCP
Browser Automation · Local stdio
Quality: 81/100 (Excellent) | Auth: No auth required
Verdict Summary: Choose Gachi Data API — Japan Station & Accessibility Data if you need specialized Browser Automation tools running via a hosted cloud SSE transport. Choose Playwright MCP if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Gachi Data API — Japan Station & Accessibility Data when:
You need dedicated capabilities in the Browser Automation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Gachi Data API — Japan Station & Accessibility Data Tools (3)
get_toilet_by_station
Accessible toilets in a Tokyo station, with `nearest_exit
get_public_toilet_by_city
Public toilets in a municipality (top 50 for large cities)
get_station_hazard
Official MLIT hazard categories at a station (flood / liquefaction / storm-surge), relayed live, cached 14 days — no derived score. Landslide & tsunami are license-restricted (`available:false` + link to official maps). Not a substitute for official hazard maps.
Playwright MCP Tools (26)
browser_close
Close the page
browser_resize
Resize the browser window
browser_console_messages
Returns all console messages
browser_handle_dialog
Handle a dialog
browser_evaluate
Evaluate JavaScript expression on page or element
browser_file_upload
Upload one or multiple files
browser_drop
Drop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.
browser_find
Search the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.
browser_fill_form
Fill multiple form fields
browser_press_key
Press a key on the keyboard
browser_type
Type text into editable element
browser_navigate
Navigate to a URL
+14 more tools listed on main page
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Gachi Data API — Japan Station & Accessibility Data Configuration
Gachi Data API — Japan Station & Accessibility Data is categorized under Browser Automation and uses a remote streaming HTTP/SSE transport. In contrast, Playwright MCP belongs to Browser Automation using local stdio subprocess. Select Gachi Data API — Japan Station & Accessibility Data when you need capabilities focused on browser automation and Playwright MCP when you require tools for browser automation.
