DataCite REST MCP for AI. Manage research metadata and DOIs via your AI agent.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
DataCite REST manages Digital Object Identifiers (DOIs) and scholarly metadata by connecting your AI agent directly to the global research registry.
You can use this MCP to retrieve detailed publication data, track provenance history, search across registered DOIs, and programmatically manage research records for academic pipelines.
What your AI can do
Create doi
Generates and registers a brand new DOI record following the JSON:API format.
Delete doi
Removes a DOI record, but only if it is currently in draft status.
Get doi
Retrieves the full metadata set associated with one specific DOI number.
Retrieve all known details for any given Digital Object Identifier.
Create, update, or delete draft DOI records according to the JSON:API standard.
Search and list DOIs using advanced filters like client names, prefixes, or resource types.
View a complete audit trail of metadata changes and discover related usage events or citations.
Get an overview of the DataCite network, including registered clients, providers, and prefixes.
Ask an AI about this
Waiting for input…
DataCite REST: 12 Tools for DOI Management
These twelve tools allow your agent to perform every major action on the DataCite network, from creating new DOIs to tracking their entire history.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using DataCite REST on VinkiusCreate Doi
Generates and registers a brand new DOI record following the JSON:API format.
Delete Doi
Removes a DOI record, but only if it is currently in draft status.
Get Doi
Retrieves the full metadata set associated with one specific DOI number.
Get Heartbeat
Checks the current operational status of the DataCite API connection.
List Activities
Retrieves a history log showing when and how metadata records have been changed over...
List Clients
Pulls a list of all connected DataCite Repository accounts.
List Dois
Retrieves a filtered list of DOI records based on criteria like provider or prefix.
List Events
Finds links between DOIs and other resources, including recorded citations and usage...
List Prefixes
Lists the available DOI prefixes used across the DataCite network.
List Providers
Retrieves a list of registered DataCite members and consortium organizations.
List Reports
Gets usage reports detailing how often specific DOI records are accessed.
Update Doi
Modifies the details of an existing DOI record, applying changes to specified attributes.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with DataCite REST, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DataCite. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking Data Provenance in Academia
Right now, tracking metadata history means jumping between different institutional web portals. You copy the DOI from one place, paste it into another system to see if the record was updated, and then manually cross-reference the changes with an external usage log. It's a painful loop of copying, pasting, and waiting for slow reports.
With this MCP, you simply tell your agent which identifier you are checking. The tool executes `list_activities`, instantly pulling every metadata change recorded in the DOI record's history. You get a clean, actionable log showing exactly what changed and when, without leaving your workflow.
Get Structured Data with DataCite REST MCP
Gone are the days of guessing which field holds the publisher name or if an affiliation is current. You no longer have to manually search through pages of unstructured text looking for key facts.
Now, you can ask your agent to `get_doi` and it returns a clean, structured JSON object containing every piece of metadata—the affiliations, the title, the resource type—ready for immediate use in any script or report. It’s that simple.
What your AI can actually do with this
This connector lets you access the central infrastructure for managing research identifiers. Instead of manually visiting multiple web portals just to find a dataset's citation details or check its status, your AI agent handles it all. You tell your agent which DOI you need, and it pulls the associated metadata—including publisher info and affiliations—directly from DataCite.
Need to track how that data has changed over time? The MCP tracks every event, giving you a full history log. When developing research tools or building automated pipelines, this is where you connect. Once connected via Vinkius, your agent acts like a dedicated research data manager, handling complex queries and records management through simple natural conversation.
019e3885-f31d-73cb-a9b7-34354763b27a Here's how it actually works
The bottom line is that you stop dealing with web forms and start talking directly to the source of academic identifiers.
Subscribe to this MCP on Vinkius and enter your specific DataCite Username and Password.
Your agent authenticates using these credentials and connects the global research data network to your workflow.
You simply ask your AI client for a DOI record, or tell it to list all active clients; the tool executes the request and returns structured metadata.
Who is this actually for?
This MCP is for data librarians, research developers, and academics who spend time manually verifying citation details or managing dataset records. If your job involves working with persistent identifiers, this cuts out hours of tedious manual lookup.
Needs to instantly pull metadata and citations for a specific publication's DOI when writing an article or compiling literature reviews.
Uses the MCP to programmatically manage, verify, and update the provenance records of multiple DOIs across different institutional datasets.
Integrates scholarly metadata into automated pipelines that process large volumes of scientific data identifiers.
What Changes When You Connect
Instead of manually checking a web portal for an update, you can use update_doi to modify existing publication details directly through a simple chat command.
Need context on who created the data? Use list_providers and list_clients to map out the entire network of scholarly contributors and repositories.
Tracking usage is critical. Running list_reports gives you immediate insight into how often certain datasets are being cited or accessed, without logging into a separate analytics dashboard.
When building research pipelines, use get_doi to pull clean metadata for any identifier, then pass that structured data directly to your next script step.
Don't just find the DOI; find its lineage. Running list_activities gives you the full audit trail of every change made to a record.
See it in action
Verifying Publication History
A data librarian needs to verify if a specific DOI has been modified since its initial publication. Instead of searching multiple version control dashboards, they ask their agent to run list_activities on the DOI. The agent returns a chronological log of every metadata change, confirming provenance.
Building Citation Maps
A researcher needs to know what other papers cited a core dataset. They instruct their agent to use list_events for the target DOI. The agent returns all linked resources and citation links, allowing the researcher to build a complete map of scholarly impact.
Onboarding New Partners
A developer needs to integrate a new research group's records into their system. They use list_clients to verify if the group is already registered, and then they can use create_doi once credentials are confirmed.
Auditing Data Integrity
A team needs a snapshot of all active records managed by their institution. They ask the agent to run list_dois, filtering by their unique prefix, generating a clean list for immediate review and auditing.
The honest tradeoffs
Searching for Metadata in General
Copying a DOI into Google or a general search engine and sifting through academic blog posts hoping to find the correct metadata.
Always use get_doi with your agent. This tool talks directly to the authoritative source, giving you structured data immediately, rather than relying on web scraping.
Updating Records Manually
Logging into a separate vendor portal and clicking through five forms to correct an author's affiliation or title.
Use the update_doi tool. Your agent handles the JSON:API payload, allowing you to push necessary corrections with one command.
Assuming Persistence
Relying on a non-DOI identifier (like a URL or title) which might change next month.
Always use the DOI. Start by running get_doi to confirm it, then rely on that persistent link for all your metadata retrievals.
When It Fits, When It Doesn't
Use this MCP if your core problem involves managing or verifying academic identifiers (DOIs) and their associated structured metadata. You need to know who published the data, when it changed, or what other works cited it. Don't use it if you just need to store general documents, like raw PDFs or internal meeting notes—for that, you need a document storage solution. If your goal is merely listing basic available identifiers across an entire academic network without deep metadata querying, list_dois is fine. But if you need the full context (provenance, usage, changes), stick to this MCP and its specific tools.
Questions you might have
How do I get the full history using DataCite REST MCP? +
You run the list_activities tool. This retrieves a detailed audit trail showing every time the metadata for a DOI was created or changed, giving you the complete provenance log.
What is the purpose of list_events in DataCite REST MCP? +
list_events finds links between a specific DOI and other resources. It's how you discover which papers cited this work or what usage metrics are attached to it.
Can I change an existing DOI record using DataCite REST MCP? +
Yes, use the update_doi tool. You provide the specific attributes and values you want changed, and the agent handles applying those necessary modifications to the live record.
What if I need a list of all available publishers? +
Use the list_providers tool. This quickly pulls a comprehensive roster of DataCite members and consortium organizations registered in the network.
What credentials do I need to authenticate when using the `get_doi` tool? +
You must use your Member API authentication credentials for full access. These credentials authorize your agent to interact with protected DOI records and metadata. You'll enter your specific DataCite username and password during setup.
How do I search across many records using the `list_dois` tool? +
The list_dois tool allows advanced filtering to narrow down your results. Instead of listing everything, you can filter by specific criteria like client account ID, provider name, or a particular prefix.
What format must the data be in when I execute `create_doi`? +
The payload for creating a new DOI record needs to strictly follow JSON:API format. This standardized structure ensures that all required fields, like metadata and identifiers, are provided correctly.
Can the `list_clients` tool confirm my repository account status? +
Yes, running list_clients retrieves a list of active DataCite Repository accounts. This confirms which member organizations or clients currently have registered access within the overall DataCite network.
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.
We've already built the connector for DataCite REST. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.