Skip to main content
Glama
vjrj

ipt-mcp

by vjrj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ipt-mcp

No user-submitted related servers found.

    Related Servers

    • geonode-mcp

      christianbraun
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and manage GeoNode resources via natural language, including metadata editing, permission changes, uploads, and ownership transfers, all under the acting user's own permissions.
      Apache 2.0

    • CKAN MCP Server

      ondata
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to search, explore, and query any CKAN open data portal through natural language, making public datasets accessible without requiring knowledge of the portal's API.
      20
      419 npm
      58
      MIT

    • WordPress MCP Server

      gaupoit
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.
      9
      MIT

    • dspace-mcp

      or-sirina
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to operate DSpace repositories through a typed interface, including SAF package building, metadata editing, scientometric harvesting, open-access PDF downloads, and repository administration.
      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

    B3.1/5.0

    Scored across 32 tools

    Disambiguation4/5

    Tools are broadly distinct: reads vs writes, resources vs mappings vs metadata, and validation stages are clearly separated. The main ambiguity is that several specialized metadata setters (basic, contacts, coverage, keywords/methods) overlap with the generic ipt_set_metadata_fields, so an agent could choose either route.

    Naming Consistency4/5

    The dominant pattern is ipt_<verb>_<noun>, with list for collections and get for single items. Minor deviations include `ipt_health` with no verb, `validate_tsv` lacking the ipt_ prefix, and `ipt_publish` being a bare verb.

    Tool Count2/5

    At 32 tools, the server is above the 25+ threshold and feels heavy for an agent to navigate. Several specialized metadata setters duplicate the generic ipt_set_metadata_fields and could be consolidated without losing functionality.

    Completeness4/5

    The surface covers the full publish lifecycle: create resources, add/configure sources, map terms, validate, publish, change visibility, and delete resources. Minor gaps exist, such as refreshing an existing URL source or directly downloading a published archive, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources