Skip to main content
Glama
idss-mesa

neon-mcp

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to neon-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • ameriflux-mcp

      idss-mesa
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to search AmeriFlux and FLUXNET eddy-covariance tower sites, check product and year availability, decode FLUXNET variable names and QC flags, and retrieve versioned citations and data-policy obligations. Also supports consented downloads and local previewing of AmeriFlux BASE/BADM, FLUXNET-1F, and FLUXNET2015 FULLSET/SUBSET files.
      11
      MIT

    • .

      idss-mesa
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to search and retrieve global biodiversity data — species taxonomy, occurrence records, datasets, map tiles, literature citations and controlled vocabularies — through a standard tool interface. It exposes the source's API as dozens of typed, paginated tools that any MCP client can call.
      58
      51 npm
      MIT

    • mcp-server-eia

      abrose1
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with structured access to the U.S. EIA Open Data API for energy data including power plants, operations, fuel prices, projections, and state CO2 emissions.
      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.2/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: searching sites, products, availability, files, locations, samples, taxonomy, and prototypes are all separated. Even similar tools like get_site vs get_product or list_files vs download_files are unambiguous due to clear nouns and descriptions.

    Naming Consistency5/5

    All tools follow a consistent neon_<verb>_<noun> pattern, with verbs like get, list, search, download, find, ping, and graphql. The naming is uniformly snake_case and predictable, making it easy to guess tool behaviors.

    Tool Count4/5

    With 20 tools, the server covers a broad domain (NEON ecological data) and each tool addresses a specific need, but the count is at the upper edge of the ideal range. Some tools like neon_graphql and neon_ping add flexibility but could be considered optional; still, the count is justifiable for the extensive API surface.

    Completeness5/5

    The server provides comprehensive coverage: search and discovery (sites, products, samples, prototypes, taxonomy), metadata retrieval (get_site, get_product, get_release, get_location, get_document), availability and citation, file listing and downloading, plus a GraphQL fallback for edge cases. It covers the full lifecycle from discovery to data access and citation, with no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources