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 VS Code Copilot?
GitHub Copilot Agent mode brings DataCite REST data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
DataCite REST in VS Code Copilot
DataCite REST and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect DataCite REST to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Arrivy
9 toolsManage field service tasks, crews, and customer bookings with Arrivy — coordinate last-mile delivery and jobs via AI.

ThePDFMaker
12 toolsTransform HTML templates into pixel-perfect PDF documents with an API designed for invoices, reports, and branded output.

Loop Subscriptions
9 toolsSubscription management for Shopify — manage recurring orders and customers via Loop.

ChurnZero
8 toolsManage customer success and health via ChurnZero — track churn scores, monitor segments, and analyze account activity directly from any AI agent.
