Skip to main content
Glama
Sign In
edi-mcp

edi-mcp

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to edi-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • mcp-datacite

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to DataCite DOIs for research datasets, enabling searching and retrieval of dataset metadata.
      99 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.
      98 npm
      MIT

    • ScienceBase MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching the USGS scientific data catalog and retrieving individual records or their hierarchical child items, returning summaries, categories, dates, contacts, web links, and download URLs for datasets, publications, and projects.
      306 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 8 tools

    Disambiguation4/5

    Tools are mostly distinct, but edi_get_package and edi_get_metadata both retrieve package-level information (summary vs full EML), and edi_list_entities overlaps with the entities section of edi_get_metadata. The descriptions clearly guide which to use, but the tiered granularity creates minor potential for misselection.

    Naming Consistency4/5

    All tools use the edi_ prefix and snake_case, with a consistent verb_noun pattern except edi_ping (verb only). This is a minor deviation, but the set remains highly readable and predictable.

    Tool Count5/5

    Eight tools are well-scoped for a data repository client, covering discovery, metadata retrieval, and health checking without redundancy. Each tool earns its place.

    Completeness2/5

    The descriptions reference edi_preview_entity and edi_download_entities as next steps, but these tools are absent from the set. This leaves a critical gap: agents can discover and inspect metadata but cannot retrieve or preview actual data, which is a core function of the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources