Compatible with every major AI agent and IDE
What is the DataCite REST MCP Server?
Connect to the DataCite REST API to interact with the global infrastructure for research data. This MCP server allows your AI agent to search, retrieve, and manage DOIs and their associated metadata.
What you can do
- DOI Management — Create, update, and delete DOI records (Draft state) with full JSON:API support.
- Metadata Retrieval — Fetch detailed metadata for any DOI, including affiliations and publisher info.
- Search & Discovery — List DOIs with advanced filtering by client, provider, prefix, or resource type.
- Provenance & Events — Track metadata changes through activities and discover citations or usage via events.
- Infrastructure Overview — List repository accounts (clients), providers, and prefixes within the DataCite network.
How it works
- Subscribe to this server
- Enter your DataCite credentials (Username and Password)
- Start managing research identifiers from Claude, Cursor, or any MCP-compatible client
No more manual searching through web portals to find research citations or metadata. Your AI acts as a dedicated research data manager.
Who is this for?
- Researchers & Academics — instantly retrieve metadata and citations for specific datasets or publications
- Data Librarians — manage DOI records and verify metadata provenance directly from their workflow
- Developers — integrate scholarly metadata and DOI registration into automated research pipelines
Built-in capabilities (12)
Requires Member API authentication (Repository account). Payload must follow JSON:API format. Create a new DOI record
Only DOIs in Draft state can be deleted. Requires Member API authentication. Delete a DOI (Draft state only)
Retrieve metadata for a specific DOI
Check API status
Retrieve metadata provenance (history of changes)
List DataCite Repository accounts
Retrieve a list of DOIs
Retrieve links between DOIs and other resources (citations, usage)
List DOI prefixes
List DataCite Members and Consortium Organizations
List usage reports
Requires Member API authentication. Only included attributes will be updated. Update an existing DOI record
Why Claude Desktop?
Claude Desktop is the definitive way to connect DataCite REST to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
DataCite REST in Claude Desktop
DataCite REST and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect DataCite REST to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for DataCite REST in Claude Desktop
The DataCite REST MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
DataCite REST for Claude Desktop
Every tool call from Claude Desktop to the DataCite REST MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for DOIs using specific metadata queries?
Yes! Use the list_dois tool with the query parameter. You can use OpenSearch query string syntax to search through all metadata fields indexed by DataCite.
How do I see the history of changes for a DOI?
You can use the list_activities tool to retrieve metadata provenance, which shows the history of changes and updates made to records in the DataCite system.
Can I delete any DOI record?
No. According to DataCite rules, only DOIs in the 'Draft' state can be deleted using the delete_doi tool. Registered or Findable DOIs cannot be deleted to ensure the persistence of research citations.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Ghost
11 toolsManage blog posts, track authors, and oversee static pages via AI agents with Ghost CMS.

AudioStack
10 toolsProduce end-to-end AI audio via AudioStack — automate high-quality speech, mixing, and mastering via AI.

Deel
10 toolsManage global contracts, team members, invoices, payments, time-off, and expenses — global HR for AI agents.

Vercel
10 toolsBring your Vercel deployment infrastructure into chat. Control project domains, trigger manual builds, and inspect deployment status natively.
