mcp-server-blm-mlrs
Provides tools to query geothermal lease data from BLM's ArcGIS FeatureServer, including retrieving lease details and searching leases with filters.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-blm-mlrsSearch for active geothermal leases in Nevada."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-blm-mlrs
An MCP server for the BLM MLRS Geothermal Leases dataset.
It exposes tools that query the U.S. Bureau of Land Management (BLM) Mineral & Land Records System (MLRS) geothermal leases ArcGIS FeatureServer and returns clean, structured lease data to any MCP client (Claude Desktop, etc.).
Data source
BLM National MLRS Geothermal Leases FeatureServer:
https://gis.blm.gov/nlsdb/rest/services/HUB/BLM_Natl_MLRS_Geothermal_Leases/FeatureServer/0Related MCP server: mcp-arcgis-montana
Tools
get_lease_details(case_number)
Retrieve full details for a single lease by its BLM case serial number.
case_number— BLM case serial number, e.g.'NVNV105806473'.
Returns a dict of lease details (case name, type, status, state, acreage, commodity, formation, production status, effective/expiration/sale dates, data source), or an error message if not found.
search_leases(state, status, effective_date_from, effective_date_to, expiration_date_from, expiration_date_to)
Search leases with optional filters. All parameters are optional; if none are given, all leases are returned (capped at 50 records).
Parameter | Field | Description |
|
| Two-letter admin state code, e.g. |
|
| Case disposition/status, e.g. |
|
| Inclusive lower bound, ISO date |
|
| Inclusive upper bound, ISO date |
|
| Inclusive lower bound, ISO date |
|
| Inclusive upper bound, ISO date |
Returns {"count": <int>, "leases": [ {lease summary}, ... ]}, or an error message on failure.
Installation
Requires Python >= 3.11.
uv syncRunning
By default the server runs over stdio, suitable for local MCP clients:
uv run python -m geothermal_leases.appIf a PORT (or DATABRICKS_APP_PORT) environment variable is set, it instead serves over HTTP on that port:
PORT=8000 uv run python -m geothermal_leases.appA health check is available at GET /health when running over HTTP.
Configuring an MCP client
Example entry for a client that launches MCP servers over stdio:
{
"mcpServers": {
"geothermal-leases": {
"command": "uv",
"args": ["run", "python", "-m", "geothermal_leases.app"],
"cwd": "/path/to/mcp-server-blm-mlrs"
}
}
}Project layout
src/geothermal_leases/
├── app.py # FastMCP server entrypoint (stdio / HTTP)
├── routes.py # Custom HTTP routes (health check)
└── tools/
├── __init__.py # Tool registration
├── _blm.py # Shared BASE_URL + date helpers
├── get_lease_details.py # get_lease_details tool
└── search_leases.py # search_leases toolThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GSA-TTS/mcp-server-blm-mlrs'
If you have feedback or need assistance with the MCP directory API, please join our Discord server