mireye-earth-mcp

# mireye-earth-mcp Expose Mireye Earth's `/v1/ask` and `/v1/fetch` endpoints to any MCP-aware agent (Claude Desktop, Claude Code, Cursor, custom agents built on the `mcp` Python SDK) as native tools — no HTTP wiring required. This is a standalone PyPI package (`mireye-earth-mcp`) with only two runtime dependencies — `httpx` and `mcp`. It does not pull in the geospatial backend, so there's no GDAL / rasterio / DuckDB build step. The server is a ~100-line stdio adapter with zero business logic: each tool handler POSTs to the deployed Mireye HTTP API and returns the response verbatim, preserving per-field provenance, citations, and honest-pattern `partial_failures`. --- ## What the agent gets Two tools, both prefixed `mireye_` so they sort together and don't collide with generic `ask` / `fetch` tools from other MCP servers: | Tool | When the agent should call it | |-----------------|------------------------------------------------------------------------------------------------| | `mireye_ask` | The caller asked a question about a US place ("is this in a flood zone?", "wildfire risk?"). | | `mireye_fetch` | The caller wants specific named fields ("elevation and slope here") or is powering a workflow. | Two matching prompts (`mireye_ask`, `mireye_fetch`) are also registered. Claude Code surfaces MCP prompts as slash commands under the form `/mcp__<server>__<prompt>` — concretely `/mcp__mireye-earth__mireye_ask` and `/mcp__mireye-earth__mireye_fetch`. The slash format isn't customizable; the main path for most users is still natural chat ("what elevation is 40.7128, -74.006?"), with the model choosing the tool. There is no third `list_fields` tool. Agents that need the catalog can hit `GET /v1/meta/fields` via plain HTTP — the endpoint sets a 1-hour `Cache-Control` and an `ETag`, so a long-lived agent fetches it once. --- ## Install — one command with `uvx` ```bash uvx mireye-e…