In-depth architectural comparison of the Arcgis Palmbeach and Arcgis Fairfax 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
Arcgis Palmbeach
Developer Tools · Local stdio
Quality: 29/100 (Emerging) | Auth: No auth required
Arcgis Fairfax
Developer Tools · Local stdio
Quality: 29/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Arcgis Palmbeach if you need specialized Developer Tools tools running via a local process. Choose Arcgis Fairfax if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Arcgis Palmbeach when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Arcgis Palmbeach is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Arcgis Fairfax belongs to Developer Tools using local stdio subprocess. Select Arcgis Palmbeach when you need capabilities focused on developer tools and Arcgis Fairfax when you require tools for developer tools.