Research Deposition MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENODO_API_KEY | Yes | Zenodo/Sandbox bearer token. Required for deposition operations. | |
| ZENODO_BASE_URL | No | Repository endpoint and part of the approval target. | https://sandbox.zenodo.org |
| ZENODO_ALLOW_PUBLISH | No | Process-level final-publication enablement. | false |
| ZENODO_MAX_UPLOAD_BYTES | No | Per-file local safety ceiling used by this server. | 52428800 |
| DEPOSITION_APPROVAL_MAX_AGE_SECONDS | No | Server-side maximum accepted receipt age. | 900 |
| DEPOSITION_APPROVAL_PUBLIC_KEY_FILE | No | Operator public Ed25519 key used to verify receipts. Final publication fails closed when unset. | |
| DEPOSITION_PUBLICATION_POLICY_VERSION | No | Policy identifier included in approval requests/receipts. Changing it invalidates older receipts. | 1 |
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 |
|---|---|
| deposition_statusA | Report deposition backend and safety configuration. Does not expose secrets. |
| validate_depositionA | Deterministically validate repository-independent research deposition metadata. Never publishes anything. |
| build_file_manifestA | Build a deterministic repository-independent SHA-256 manifest from explicit include/exclude rules. Never uploads or publishes files. |
| build_publication_packageB | Build canonical metadata + file manifest and compute the package SHA-256 identity. Never writes to a repository. |
| create_draftB | Validate metadata and create an unpublished repository draft. Default backend is Zenodo Sandbox. |
| get_draftC | Retrieve an existing unpublished deposition draft. |
| update_draftB | Validate and replace metadata on an existing unpublished draft. |
| upload_fileB | Upload a local file to an existing draft. Never publishes the draft. |
| publication_reviewA | Rebuild the exact package identity, retrieve the draft, and return the approval request a human operator may sign out-of-band. Does not publish. |
| publish_draftC | Publish only when process-level publication is enabled and a valid short-lived operator-signed receipt matches a freshly recomputed package, repository endpoint, draft, and policy. |
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 10 tools
Each tool has a clearly distinct responsibility in the deposition lifecycle—status, validation, manifest building, package building, draft creation, retrieval, update, file upload, review, and publication. Even the two validation-related tools (validate_deposition and create_draft) are separated by action, and descriptions clarify their boundaries.
Most tools follow a consistent verb_noun pattern (validate_deposition, build_file_manifest, create_draft, upload_file, publish_draft), but a few use noun-first names (deposition_status, publication_review) that break the pattern slightly. This is a minor deviation and does not impede understanding.
With 10 tools covering the complete deposition workflow, the count is well within the ideal 3-15 range. Each tool serves a necessary, non-redundant role in the pipeline, and none feel extraneous.
The tool set covers the full deposition lifecycle: validation, manifest/package building, draft creation/retrieval/update, file upload, review, and publication. There are no obvious gaps for the stated purpose—only minor absent operations like listing or deleting drafts, which are not critical to the core workflow.