Skip to main content
Glama
idss-mesa

ameriflux-mcp

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ameriflux-mcp

No user-submitted related servers found.

    Related Servers

    • neon-mcp

      idss-mesa
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to discover NEON ecological data products and sites, check data availability, list and download data files, and generate citations via the NEON Data API.
      20
      MIT

    • edi-mcp

      idss-mesa
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to search, inspect, preview, download, and cite LTER and EDI ecological data packages from the PASTA+ repository, including metadata, entities, citations, change feeds, and provenance. An API key unlocks quality reports, lineage, read counts, and other privileged PASTA endpoints.
      8
      MIT

    • NASA CMR MCP Server

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search Earth-science dataset collections by keyword, platform, instrument, time range, or bounding box; fetch full collection metadata; and list individual data granules with direct download links.
      12 npm
      MIT

    • mcp-dryad

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to keylessly search open research datasets by full-text query and fetch full metadata plus download links for a dataset by DOI.
      238 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools occupy clearly separate niches: search_* returns candidate lists, get_* pulls one entity, and the local-file tools (list_files, preview_data, read_bif) are distinct from the API tools. A few pairs are close — describe_variables vs. search_variables (both about variable names) and get_badm vs. read_bif (BADM metadata via API vs. from a local file) — but the descriptions explicitly anchor them to different sources and workflows.

    Naming Consistency5/5

    Every tool carries the amf_ prefix and follows a clean snake_case verb_noun pattern (get_site, search_sites, describe_variables, read_bif, list_files), with only the conventional bare 'ping' deviating. The naming is fully predictable and reinforces the search/get/describe groupings.

    Tool Count5/5

    Eleven tools is a well-scoped set for a site-catalog + metadata + local-file-inspection server, and each tool maps to a concrete step in the discovery-to-analysis workflow. No filler or redundant wrappers are present.

    Completeness3/5

    The discovery, metadata, citation and local-file reading surface is rich, but the download step appears absent from the tool list even though amf_ping describes configured download identities, enabled downloads, and 'which tools need it' — leaving a gap between finding a site and reading its data. There is also no write/export or bulk-extraction operation, so agents may hit a dead end after previewing files.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources