loading…
Search for a command to run...
loading…
MCP server providing access to the BERtron API for aggregating genomic and environmental data from multiple BER data sources, enabling geospatial search and hea
MCP server providing access to the BERtron API for aggregating genomic and environmental data from multiple BER data sources, enabling geospatial search and health checks.
A Model Context Protocol (MCP) server providing access to the BERtron API, which aggregates genomic and environmental data from multiple Biological and Environmental Research (BER) data sources including EMSL, ESS-DIVE, JGI, MONET, and NMDC.
# Run directly without installing
uvx --from git+https://github.com/ber-data/bertron-mcp.git bertron-mcp
# Or install first, then run
uvx --from git+https://github.com/ber-data/bertron-mcp.git bertron-mcp --version
git clone https://github.com/ber-data/bertron-mcp.git
cd bertron-mcp
make dev
pip install bertron-mcp
geosearchSearch for entities within a specified distance of geographic coordinates.
Parameters:
latitude (float): Latitude coordinate (-90.0 to 90.0)longitude (float): Longitude coordinate (-180.0 to 180.0) search_radius_km (float, optional): Search radius in kilometers (default: 1.0)Returns: QueryResponse with entities, count, and metadata
bbox_searchSearch for entities within a rectangular geographic bounding box.
Parameters:
southwest_lat (float): Southwest corner latitude (-90.0 to 90.0)southwest_lng (float): Southwest corner longitude (-180.0 to 180.0)northeast_lat (float): Northeast corner latitude (-90.0 to 90.0)northeast_lng (float): Northeast corner longitude (-180.0 to 180.0)Returns: QueryResponse with entities within the bounding box
entity_lookupRetrieve detailed information for a specific entity by its unique ID.
Parameters:
entity_id (string): Unique identifier of the entity (e.g., "nmdc:bsm-12-abc123")Returns: Entity object with complete metadata
advanced_queryExecute complex MongoDB queries with filtering, projection, and sorting.
Parameters:
filter_dict (dict, optional): MongoDB filter criteria (e.g., {"entity_type": "sample"})projection (dict, optional): Fields to include/exclude (e.g., {"name": 1, "coordinates": 1})skip (int, optional): Number of documents to skip for pagination (default: 0)limit (int, optional): Maximum number of documents to return (default: 100)sort (dict, optional): Sort criteria (e.g., {"name": 1} for ascending)Returns: QueryResponse with matching entities
search_by_sourceFind entities from a specific BER data source.
Parameters:
source (string): BER data source name (EMSL, ESS-DIVE, JGI, NMDC, MONET)Returns: QueryResponse with entities from the specified source
search_by_typeFind entities of a specific entity type.
Parameters:
entity_type (string): Entity type (biodata, sample, sequence, taxon, jgi_biosample)Returns: QueryResponse with entities of the specified type
search_by_nameSearch for entities by name using regex pattern matching.
Parameters:
name_pattern (string): Name pattern to search for (supports regex)case_sensitive (bool, optional): Whether search should be case sensitive (default: False)Returns: QueryResponse with entities matching the name pattern
health_checkCheck the health status of the BERtron API.
Parameters: None
Returns: Dictionary with web_server and database boolean status
To prevent overwhelming responses and protect system resources, the following limits are enforced:
When limits are applied, tools automatically report constraints in the response metadata:
{
"entities": [...],
"count": 1000,
"metadata": {
"constraints_applied": {
"requested_limit": 5000,
"actual_limit": 1000,
"reason": "Exceeded maximum limit of 1000"
}
}
}
The following tools accept optional limit parameters:
search_by_source(source, limit=100)search_by_type(entity_type, limit=100) search_by_name(name_pattern, case_sensitive=False, limit=100)advanced_query(filter_dict=None, limit=100, skip=0, ...)advanced_query requires filter criteria to prevent accidental full database dumpsInstall dependencies for development:
make dev
Run the complete test suite:
make all
Test specific components:
# API integration tests
make test-integration
# MCP protocol tests
make test-mcp
make test-mcp-extended
# Test with Claude CLI
make test-claude-mcp
# Version check
make test-version
Option 1: From GitHub (Recommended)
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"bertron-mcp": {
"command": "uvx",
"args": ["--from", "git+https://github.com/ber-data/bertron-mcp.git", "bertron-mcp"]
}
}
}
Option 2: Local Development
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"bertron-mcp": {
"command": "uv",
"args": ["run", "python", "src/bertron_mcp/main.py"],
"cwd": "/path/to/bertron-mcp"
}
}
}
From GitHub:
claude mcp add bertron-mcp "uvx --from git+https://github.com/ber-data/bertron-mcp.git bertron-mcp"
Local development:
claude mcp add -s project bertron-mcp uv run python src/bertron_mcp/main.py
Production (after publishing to PyPI):
claude mcp add -s project bertron-mcp uvx bertron-mcp
From GitHub:
goose session --with-extension "uvx --from git+https://github.com/ber-data/bertron-mcp.git bertron-mcp"
Local development:
goose session --with-extension "uv run python src/bertron_mcp/main.py"
Search for genomic samples near Orlando, FL within 100km radius:
> Use the bertron-mcp to search for entities near latitude 28.5383, longitude -81.3792 within 100km
Search for entities in a bounding box covering Yellowstone National Park:
> Use bbox_search to find entities between southwest corner (44.0, -125.0) and northeast corner (49.0, -110.0)
Find all NMDC sample entities:
> Search for all sample entities from the NMDC data source
Look up detailed information for a specific entity:
> Use entity_lookup to get details for entity ID "nmdc:bsm-12-abc123"
# Test geosearch tool
echo '{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "geosearch", "arguments": {"latitude": 28.5383, "longitude": -81.3792, "search_radius_km": 100.0}}, "id": 1}' | uv run python src/bertron_mcp/main.py
# Test bounding box search
echo '{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "bbox_search", "arguments": {"southwest_lat": 44.0, "southwest_lng": -125.0, "northeast_lat": 49.0, "northeast_lng": -110.0}}, "id": 2}' | uv run python src/bertron_mcp/main.py
# Test search by data source
echo '{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "search_by_source", "arguments": {"source": "NMDC"}}, "id": 3}' | uv run python src/bertron_mcp/main.py
# Test advanced query with filtering
echo '{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "advanced_query", "arguments": {"filter_dict": {"entity_type": "sample"}, "limit": 10}}, "id": 4}' | uv run python src/bertron_mcp/main.py
# Format and lint code
make format
make lint
# Type checking
make mypy
# Dependency analysis
make deptry
# Build package
make build
# Full release workflow
make release
BERtron aggregates data from:
git checkout -b feature/your-featuremake allgit commit -m "Add your feature"git push origin feature/your-featureBSD-3-Clause
Run in your terminal:
claude mcp add bertron-mcp -- npx Security
Low riskAutomated heuristic from public metadata — not a security guarantee.