Skip to main content
Mireye’s supported MCP endpoint is https://api.mireye.com/mcp, using Streamable HTTP and OAuth. Add that URL as a remote MCP server in a client that supports remote authorization, then complete the browser sign-in flow.

​
Guided setup

Open Mireye setup, accept the current terms, and copy the setup prompt into Claude Code, Codex, or Cursor. The pinned mireye-mcp 0.7.2 helper installs a native remote connection to the hosted URL and the use-mireye skill. It does not run a local stdio server. It preserves unrelated configuration and refuses to overwrite custom Mireye entries. The helper saves your scoped API key privately for HTTP calls and diagnostics; credentials are not embedded in the MCP configuration. Complete the client’s browser OAuth flow for hosted MCP. The page’s first-call milestone proves a free HTTP Fetch, not a completed OAuth grant. Copying again reuses a valid setup key; revoked or outdated setup keys are replaced without granting more welcome funds.

​
Manual setup

For Claude Code:
Run /mcp and finish authorization. Client menus vary; the endpoint and OAuth contract are the same. See Authentication for current terms and credential permissions.

​
Verify the connection

The tools list contains eight tools: mireye_fetch, mireye_geocode, mireye_enrich, mireye_search, mireye_ask, mireye_proximity, mireye_request_field and mireye_field_request_status. Start with a free call:
Send it to mireye_fetch. Read mireye://catalog/fields, mireye://catalog/presets and mireye://catalog/us-envelope to discover eligible free fields, bundles and geographic bounds. Use the tool reference for paid operations and retry controls. Before using Search, configure the client’s tool timeout to at least 210 seconds. Search and its optional enrichment share a 180-second server budget. A shorter host timeout can hide a completed or partial result; recover the same paid operation instead of starting another one. Follow Find and enrich a parcel for a one-result walkthrough with explicit field selection, spending ceilings and result checks.

​
Understand the first-call check

Agent onboarding can issue an opaque API key and record a successful HTTP Fetch. The helper can install client configuration, but HTTP progress does not authorize hosted MCP. Complete this client’s OAuth flow and verify its advertised tools before treating the MCP connection as ready.

​
Migrate a local installation

The local mireye-mcp / mireye-earth-mcp adapter and device-login flow are retired. Remove the local server entry from your client’s configuration and add the hosted URL above. Existing installed binaries are not updated by this release. Do not keep both entries under the same server name. Old Lookup and Resolve calls return an explicit migration error. Use Enrich for parcel data, free Fetch for public coordinate fields, or Geocode for address coordinates. Accept current terms and reconnect OAuth to obtain licensed-data permissions; old connections do not gain these permissions automatically.