Skip to main content
Glama
4Science

DSpace MCP Server

by 4Science
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to DSpace MCP Server

No user-submitted related servers found.

    Related Servers

    • dspace-mcp

      or-sirina
      A
      license
      Not graded
      quality
      B
      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

    • dspace-mcp

      mpasternak
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that enables natural language querying of DSpace 7+ repositories via the REST API, allowing users to search, retrieve items, and analyze repository data.
      53 PyPI
      2
      MIT

    • mcp-obsidian

      OleksandrKucherenko
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Obsidian vaults via the Local REST API to search notes, retrieve content, and perform semantic searches. It features self-healing multi-URL connectivity and supports both stdio and HTTP transports for flexible deployment.
      53 npm
      13
      MIT

    • Solr MCP

      kevinbtalbert
      A
      license
      A
      quality
      B
      maintenance
      Lets AI assistants connect to Apache Solr deployments to enumerate collections and schemas, run full-text and filtered queries, apply faceting and sorting, and issue SQL or vector-semantic searches without building custom API glue. Communicates over stdio or SSE and requires minimal environment configuration instead of app-specific credentials or mandatory ZooKeeper wiring.
      7
      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

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct target and action: auth tools (status/login/logout), hierarchy (list_communities, list_collections), retrieval (search, get_item), and mutation tools. The only potentially confusable pair — create_item vs create_workspace_item and update_item_metadata vs update_workspace_item — is explicitly disambiguated by the archived-vs-workspace distinction in the descriptions.

    Naming Consistency5/5

    All 14 tools use a uniform snake_case convention with a consistent dspace_ prefix, and verbs (list/get/create/update/delete/upload/login/logout/search) are used predictably across resource nouns. No camelCase or mixed styles appear anywhere.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and each one maps to a distinct capability (auth lifecycle, hierarchy browsing, item CRUD, bitstream upload, workspace workflow). Nothing feels redundant or padded.

    Completeness3/5

    Item CRUD plus bitstream upload and a read side (communities/collections/search) are covered, but the workspace workflow is a dead end: create_workspace_item's own description says to 'submit for review' yet no submit tool exists, and delete_workspace_item, bitstream download, and community/collection management are absent. These gaps will force agents to abandon the documented deposit flow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources