mireye-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIREYE_BASE_URL | No | HTTP base URL the tools POST to. | https://api.mireye.com |
| MIREYE_TIMEOUT_S | No | Per-request timeout in seconds. | 60 |
| MIREYE_BEARER_TOKEN | No | Optional Mireye bearer token. Overrides stored credentials for tool calls. | |
| MIREYE_MCP_CREDENTIALS_FILE | No | Stored token path used by login/status/logout. | ~/.config/mireye-mcp/credentials.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mireye_askA | Answer a natural-language question about a US coordinate, with citations to authoritative federal data sources. Returns the answer plus per-citation provenance (source, source URL, fetched_at, confidence). Use this when the caller has a specific question about a place (e.g. 'is this in a flood zone?', 'what's the wildfire risk here?', 'what kind of building is at this address?'). |
| mireye_fetchA | Fetch specific data fields at a US coordinate with full provenance per field. Use this when the caller knows exactly which fields they need (e.g. 'elevation and slope at this point') or wants to power a custom workflow. Each field includes its value, source, source URL, fetched_at timestamp, and confidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| mireye_ask | Ask Mireye Earth a natural-language question about a US coordinate. |
| mireye_fetch | Fetch specific Mireye Earth fields (or a preset) at a US coordinate. |
| mireye_site_report | Create a concise site report using the site_selection preset. |
| mireye_flood_check | Assess flood-relevant signals using the flood_risk preset. |
| mireye_wildfire_underwrite | Assess wildfire underwriting signals using the wildfire preset. |
| mireye_pick_fields | Use catalog resources to choose fields before calling mireye_fetch. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mireye_catalog_fields | All public Mireye field definitions with descriptions, sources, hints, and TTLs. |
| mireye_catalog_presets | Preset names and their field expansions for mireye_fetch. |
| mireye_us_envelope | Supported latitude and longitude bounds for Mireye coordinate tools. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: mireye_ask handles natural-language questions with implicit field selection, while mireye_fetch retrieves explicitly specified data fields. There is no overlap or ambiguity.
Both tools follow the same 'mireye_<verb>' pattern with snake_case, using descriptive verbs ('ask' and 'fetch'). The naming is consistent and predictable.
With only two tools, the server is minimal but scoped appropriately for its purpose of US coordinate data queries. It could potentially benefit from a metadata tool, but the count is not unreasonable for the stated domain.
The server covers the two primary interaction modes: asking questions and fetching specific fields. It may lack a discovery or listing tool, but the existing tools provide a full workflow for obtaining data with provenance.