Back to MCP directory
publicPublicdnsLocal runtime

macrostrat-mcp

使克劳德能够通过自然语言查询Macrostrat API的综合地质数据,包括地质单元、地层柱、矿物和时间尺度。

article

README

MseeP.ai Security Assessment Badge

macrostrat-mcp

MCP server for Macrostrat API

smithery badge

Macrostrat Server MCP server

An MCP server implementation for providing access to the Macrostrat API within Claude Desktop.

Overview

This Model Context Protocol (MCP) server enables AI assistants and applications to:

  • Query comprehensive geologic data and information provided by the Macrostrat API
  • Access geologic units, columns, minerals, timescales, and more
  • Get geologic map tiles that the LLM can interpret (questionable utility, but might be useful for some applications)
  • Analyze geologic data to improve geological understanding
  • Create graphics and perform data analysis from the data

Users can run queries using natural language.

Sample Output

Q. What is the geologic history of Nashville, TN?

A. Let me check the geological data for Nashville's location.

View Result from find-units from macrostrat (local)

{
  "lat": 36.1627,
  "lng": -86.7816,
  "responseType": "long"
}

Geological History of Nashville, Tennessee

  1. Mesoproterozoic Basement (1.6-1.1 billion years ago)
  • Igneous basement rocks (granite and rhyolite)
  • Part of the ancient North American craton
  1. Early-Middle Cambrian (518-504 million years ago)
  • Rome Formation: Mixed carbonate-siliciclastic sediments
  • Shallow marine environment
  • Part of the developing continental shelf
  1. Middle-Late Cambrian (504-498 million years ago)
  • Conasauga Formation: Limestone and mixed sediments
  • Continued marine deposition
  • Alternating limestone and shale indicating fluctuating sea levels
  1. Late Cambrian-Early Ordovician (498-470 million years ago)
  • Knox Dolomite: Massive dolomite sequence
  • Extensive shallow marine platform
  • Up to 1,200 meters thick
  • Represents long period of stable marine conditions
  1. Middle-Late Ordovician (470-443 million years ago) Several important formations:
  • Stones River Group (including Murfreesboro, Pierce, Lebanon Limestones)
  • Nashville Group (including Hermitage, Bigby-Cannon, Catheys Formations)
  • Primarily limestone deposits
  • Rich in fossils
  • Shallow marine environment
  • Multiple cycles of sea level change
  1. Early-Middle Silurian (443-423 million years ago)
  • Brassfield through Decatur Formations
  • Continued marine limestone deposition
  • Various marine environments from shallow to deeper water
  1. Middle Devonian-Early Mississippian (390-357 million years ago)
  • Pegram Formation through Chattanooga Shale
  • Shift to more clastic (shale) deposition
  • Chattanooga Shale represents deeper, oxygen-poor conditions
  1. Early-Late Mississippian (357-331 million years ago) Several limestone formations:
  • Fort Payne Formation
  • Warsaw Limestone
  • St. Louis Limestone
  • Monteagle Limestone
  • Hartselle Formation
  • Return to carbonate platform conditions
  • Diverse marine environments
  1. Cenozoic to Present
  • Long period of erosion and exposure
  • Development of the current landscape
  • Formation of the Nashville Dome structure
  • River and stream deposits

Key Features

  • The area was predominantly a marine environment for most of its geological history
  • Dominated by limestone formations indicating warm, shallow seas
  • Multiple cycles of sea level change
  • Rich fossil record, especially in Ordovician rocks
  • Part of the Nashville Dome structural feature
  • Long periods of erosion have removed younger rocks
  • Current topography shaped by differential erosion of various limestone units

Present Day Bedrock

The bedrock of Nashville today consists primarily of Ordovician limestone formations exposed at the surface, particularly the Stones River and Nashville Group limestones. These rocks are well exposed in many areas and have influenced the development of local karst topography, including caves and sinkholes that are common in the region.

Installation

Installing via Smithery

To install Macrostrat API Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @blake365/macrostrat-mcp --client claude

Extra Steps

If you want to make changes to the server you can do so by editing the src/index.ts file.

  • Run npm install to install dependencies
  • Run npm run build to build the server
  • Quit and restart Claude Desktop after making changes

Connecting with Claude Desktop

  1. Open your Claude Desktop configuration at:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add the server configuration:

{
    "mcpServers": {
        "macrostrat": {
            "command": "node",
            "args": [
                "/Full/Route/to/Folder/macrostrat/build/index.js"
            ]
        }
    }
}
  1. Close/Quit then restart Claude Desktop

Once you restart you should see an icon for search and tools. Click this button to see the MCP tools available.

Troubleshooting

If you get errors when running the server you may need to provide the full path to the node command. For example, on macOS: /usr/local/bin/node

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client