Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Earth Agent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
87/100
trust score
35
downloads in 30d
local
runs on your machine
17
tools declared
What it does
MCP Server for Earth Agent - exposes Google Earth Engine tools to AI assistants like Claude Code, Cursor, and Zed
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user earth-agent-mcp '--' npx -y earth-agent-mcp
# 2 — ask your agent for something these tools do
# weather, date_time, wait and 14 more
Earth Agent costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WYAll 1 server
wybert1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Earth Agent as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user earth-agent-mcp '--' npx -y earth-agent-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get current weather for a location. Returns temperature, conditions, humidity, wind speed, etc. Useful when the user asks about weather conditions for a study area.
No parameter schema on file.
Get current date and time. Returns the current date and time, optionally in a specific timezone. Useful for timestamping operations or understanding when data was collected.
No parameter schema on file.
Wait for a specified number of seconds. Use this when you need to wait for: - Code execution to complete - Map layers to render - Data to load Maximum wait time is 60 seconds.
No parameter schema on file.
Read the current code from the Google Earth Engine Code Editor. Returns the full content of the code editor, which can be used to understand the current state before making edits.
No parameter schema on file.
Edit code in the GEE editor using old_string/new_string replacement. This tool finds the exact old_string in the editor and replaces it with new_string. The old_string must match exactly (including whitespace and indentation). Use this for targeted edits to existing code.
No parameter schema on file.
Overwrite the entire Google Earth Engine Code Editor with new code. This replaces ALL content in the editor. Use this when: - Starting fresh with new code - The existing code is not relevant - Major rewrites are needed WARNING: This will delete all existing code in the editor!
No parameter schema on file.
Undo the last code edit in the Google Earth Engine editor. Use this to revert the most recent change if something went wrong.
No parameter schema on file.
Execute the current code in the Google Earth Engine Code Editor. This clicks the
No parameter schema on file.
Take a screenshot of the Google Earth Engine interface. Returns a screenshot image showing the current state of the GEE Code Editor, including the map, console, and any visualizations. Useful for: - Seeing map layer results - Checking chart visualizations - Debugging visual issues
No parameter schema on file.
Get an accessibility snapshot of the Google Earth Engine page. Returns a YAML representation of the DOM accessibility tree, showing interactive elements with their reference IDs. Useful for: - Understanding page structure - Finding elements to click - Debugging UI interactions
No parameter schema on file.
Read the output from the Google Earth Engine console. Returns the current console output, including: - Print statements from code execution - Error messages - Task status messages Use this after running code to check results.
No parameter schema on file.
Get the current map position and bounds in Google Earth Engine. Returns: - Center coordinates (latitude, longitude) - Zoom level - Visible bounds
No parameter schema on file.
Read the Inspector panel output in Google Earth Engine. Returns data from the Inspector panel, including: - Pixel values at clicked locations - Layer information - Band values for image layers
No parameter schema on file.
Clear the Google Earth Engine map, inspector, and console. Resets the environment by: - Clearing map layers - Clearing inspector data - Clearing console output Use this to start fresh or clean up between operations.
No parameter schema on file.
Search Google Earth Engine documentation and datasets. Search types: -
No parameter schema on file.
Click an element in the GEE interface by its reference ID. Use gee_snapshot first to find element reference IDs, then use this tool to interact with buttons, links, and other clickable elements.
No parameter schema on file.
Click at a specific screen position in the GEE interface. Useful for clicking on map locations or elements without reference IDs.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Earth Agent or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
BTrust score 87 / 100
Release 1.3.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score94
Client score87
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest55e9c9216d9339b5be4fa995425afaa48bf62bc8389b4b9726947c17098e4ea7
Score vectorthreat 94 → client 87
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest55e9c9216d9339b5
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.3.0. Pin a release below and the command asks for exactly that one.
1.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Earth Agent can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.