Gachi Data API — Japan Station & Accessibility Data vs Droidmind
In-depth architectural comparison of the Gachi Data API — Japan Station & Accessibility Data and Droidmind 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
Droidmind
Browser Automation · Local stdio
Quality: 56/100 (Good) | 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 Droidmind 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).
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: ANDROID_SERIAL, ADB_SERVER_SOCKET.
Primary tools included: Device connection and property inspection, System log access including logcat, ANR, crash, battery, File system browsing and file operations on device.
Deep, obscure Japanese station, accessibility & hazard data for AI agents. English-first.
Control Android devices with AI through MCP, enabling device control, debugging, system analysis, and UI automation with a comprehensive security framework.
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.
Droidmind Tools (6)
Device connection and property inspection
System log access including logcat, ANR, crash, battery
File system browsing and file operations on device
App lifecycle management and manifest inspection
UI automation with taps, swipes, key presses
Secure shell command execution with validation
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, Droidmind 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 Droidmind when you require tools for browser automation.