Macrostrat
Access geologic data from the Macrostrat API, including units, columns, minerals, and timescales.
macrostrat-mcp
MCP server for Macrostrat API
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
- Mesoproterozoic Basement (1.6-1.1 billion years ago)
- Igneous basement rocks (granite and rhyolite)
- Part of the ancient North American craton
- Early-Middle Cambrian (518-504 million years ago)
- Rome Formation: Mixed carbonate-siliciclastic sediments
- Shallow marine environment
- Part of the developing continental shelf
- 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
- 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
- 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
- Early-Middle Silurian (443-423 million years ago)
- Brassfield through Decatur Formations
- Continued marine limestone deposition
- Various marine environments from shallow to deeper water
- 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
- 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
- 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 installto install dependencies - Run
npm run buildto build the server - Quit and restart Claude Desktop after making changes
Connecting with Claude Desktop
-
Open your Claude Desktop configuration at:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Add the server configuration:
{
"mcpServers": {
"macrostrat": {
"command": "node",
"args": [
"/Full/Route/to/Folder/macrostrat/build/index.js"
]
}
}
}
- 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
Related Servers
CData SAP Hybris C4C
A read-only MCP server for querying live SAP Hybris C4C data, powered by the CData JDBC Driver.
PostgreSQL Multi-Schema
Provides read-only access to PostgreSQL databases with multi-schema support, allowing LLMs to inspect schemas and execute queries across different namespaces.
BigCommerce by CData
A read-only MCP server for BigCommerce, enabling LLMs to query live data using the CData JDBC Driver.
KuzuMem-MCP
A distributed memory bank MCP tool that stores memories in a KùzuDB graph database, with repository and branch filtering capabilities.
MCP Toolbox for Databases
Open source MCP server specializing in easy, fast, and secure tools for Databases.
Redshift MCP Server
An MCP server for Amazon Redshift, allowing AI assistants to interact with Redshift databases.
Mem0 MCP
Integrates with Mem0.ai to provide persistent memory capabilities for LLMs, supporting cloud, Supabase, and local storage.
CData Amazon Redshift
Access and manage Amazon Redshift data using the CData MCP Server, which requires an external CData JDBC Driver.
Solana MCP Server
Provides comprehensive access to Solana blockchain data using 21 essential RPC methods.
KnowledgeGraph MCP Server
Enables persistent knowledge storage for Claude using a knowledge graph with multiple database backends like PostgreSQL and SQLite.
