mcp-rwee: Four Tools, and arcpy Runs on Another Machine
In my post arcpi: Not Everything Needs an MCP to Be Agentic , I let an agent call the ArcGIS REST API directly, with no MCP server in front of it. This time I have the opposite problem. My data and arcpy are on a Windows machine with ArcGIS Pro. Claude Code runs on my Mac. arcpy has no REST API, and it does not run on a Mac. So here, a small MCP server earns its keep. The server is mcp-rwee . The name is its tool list: r ead, w rite, e dit and e xecute. The client writes a Python script on the Windows machine, runs it there and answers from the printed output. In this post, I explain how it works, what one real question looked like, and what Windows taught me that macOS did not. Four tools and a prompt file The server has exactly four tools and one prompt. There is no buffer tool, no select_by_location tool and no list_layers tool. arcpy already has all of these. The client writes the script that calls them. read , write and edit work on text files on the Windows machin...