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 Cursor?
Cursor's Agent mode turns DataCite REST into an in-editor superpower. Ask Cursor to generate code using live data from DataCite REST and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
DataCite REST in Cursor
DataCite REST and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect DataCite REST to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Google Air Quality
2 toolsUniversal air quality intelligence — get Google-powered AQI, pollutants, and health advice via AI.

Shopify Discount Creator
1 toolsThis MCP does exactly one thing: it creates unique percentage discount codes in your Shopify store on the fly. Incredible for giving your AI agent the power to prevent cart abandonment during a chat.

Maropost
11 toolsAutomate marketing and commerce via Maropost — manage contacts, campaigns, and workflows.

ImageCharts
10 toolsGenerate charts and graphs as images from URL parameters with a simple API that creates data visualizations on the fly.
