DSpace MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (Lambda/dev) | 8080 |
| DSPACE_BASE_URL | No | DSpace REST API base URL | https://sandbox.dspace.org/server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dspace_loginA | Authenticate with a DSpace instance. Provide EITHER a JWT token directly, OR username + password for password-based login. The session persists for subsequent tool calls. |
| dspace_auth_statusB | Check the current authentication status with the DSpace instance. |
| dspace_logoutA | Logout from the DSpace instance, invalidating the current JWT token. |
| dspace_searchC | Search DSpace for items, communities, or collections. Supports full-text queries, type filtering, scoping to a container, and advanced filters. |
| dspace_get_itemB | Get a DSpace item by UUID, including all metadata. |
| dspace_list_communitiesB | List top-level communities in the DSpace repository. |
| dspace_list_collectionsB | List collections, optionally filtered to a specific community. |
| dspace_create_itemA | Create an archived item directly in DSpace (admin only, bypasses submission workflow). The item is immediately visible in the repository. |
| dspace_update_item_metadataB | Update metadata on an existing DSpace item using JSON Patch (RFC 6902). Supports add, remove, replace, and move operations on metadata fields. |
| dspace_delete_itemA | Permanently delete an item from DSpace by UUID (admin only). This is irreversible: the item and its bundles/bitstreams are removed from the repository. |
| dspace_upload_bitstreamA | Upload a local file as a bitstream (attachment) to a DSpace item (admin only). The file is added to the item's bundle (default "ORIGINAL", where DSpace stores primary files); the bundle is created automatically if it does not exist. |
| dspace_create_workspace_itemA | Create a new workspace item (submission) in DSpace. This starts the standard deposit workflow. After creation, use dspace_update_workspace_item to add metadata, then submit for review. |
| dspace_update_workspace_itemB | Update metadata on a workspace item (submission in progress) using JSON Patch. |
| dspace_list_workspace_itemsB | List workspace items (submissions in progress) for the current user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
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.
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.
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.
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.