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

    • 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.
      151 npm
      13
      MIT

    • Obsidian MCP Server

      igorilic
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Obsidian vaults for creating, reading, searching, and managing notes, daily notes, TODOs, session reports, and backlinks through both stdio and HTTP/SSE transports.
      10
      3,445 npm
      4
      MIT

    • Git RAG MCP Server

      vamsi-desu
      F
      license
      B
      quality
      C
      maintenance
      Connects an LLM to specialized MCP servers via stdio, enabling authenticated GitHub repository, issue, file, and code operations alongside TF-IDF retrieval over employee PDF records and QA test-case generation and result validation. It exposes tools, a read-only resource, and reusable prompt templates so a client can discover and orchestrate multiple capabilities in one workflow.
      3
      -

    • Synology MCP Server

      Ceyeborg
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants such as Claude, Cursor, Continue, and Codeium to manage files and downloads on Synology NAS devices through secure authenticated sessions. Supports Docker, PyPI, stdio, Streamable HTTP, and WebSocket deployment modes.
      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