Bring Open Access
to Cursor
Learn how to connect CORE (Open Access Research) to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the CORE (Open Access Research) MCP Server?
Connect to CORE, the world's largest aggregator of open access research papers. This MCP server allows your AI agent to search, retrieve, and analyze millions of scholarly articles, journals, and institutional repositories through natural conversation.
What you can do
- Global Search — Search across all CORE resources including articles, journals, and repositories using a single text query.
- Article Retrieval — Fetch full metadata, version history, and direct PDF download links for specific research papers using CORE IDs.
- Journal & Repository Discovery — Search and inspect specific journals by ISSN or explore institutional repositories to find authoritative sources.
- OAI Resolution — Resolve Open Archives Initiative (OAI) identifiers to access original metadata and repository pages.
- Deep Metadata Inspection — Analyze article history and updates to ensure you are working with the latest scientific information.
How it works
- Subscribe to this server
- Enter your CORE API Key
- Start researching directly from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Researchers & Academics — quickly find relevant papers and download PDFs without leaving your writing or coding environment.
- Students — gather citations, explore related research history, and find open access versions of paywalled content.
- Data Scientists — access a massive corpus of open access metadata for literature reviews and scientific data analysis.
Built-in capabilities (10)
Get a specific article by CORE ID
Get the history of an article
Get the PDF download URL for an article
Get a specific journal by ISSN
Get a specific repository by ID
Global search across CORE
Resolve an OAI identifier
Search for articles
Search for journals
Search for repositories
Why Cursor?
Cursor's Agent mode turns CORE (Open Access Research) into an in-editor superpower. Ask Cursor to generate code using live data from CORE (Open Access Research) and it fetches, processes, and writes. all in a single agentic loop. 10 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
CORE (Open Access Research) in Cursor
CORE (Open Access Research) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect CORE (Open Access Research) 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 CORE (Open Access Research) in Cursor
The CORE (Open Access Research) 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 10 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
CORE (Open Access Research) for Cursor
Every tool call from Cursor to the CORE (Open Access Research) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I get the PDF of a specific research article?
Use the get_article_pdf tool with the CORE Article ID. The agent will return the direct download URL for the open access PDF version of the paper.
Can I search for specific journals or repositories?
Yes! You can use search_journals or search_repositories for general text queries, or use get_journal (with an ISSN) and get_repository (with a Repository ID) for direct lookups.
What does the OAI resolution tool do?
The resolve_oai tool takes an OAI identifier (like oai:oro.open.ac.uk:75049) and resolves it to the CORE metadata page or the original repository link, helping you find the source of the research.
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 →
Make.com Webhook Trigger
1 toolsThis MCP does exactly one thing: it sends JSON payloads to Make.com Webhooks. That's its only function. Incredible for connecting AI agents to thousands of visual automation workflows instantly.
Monnify
10 toolsManage payments and virtual accounts in Nigeria via Monnify — track transactions and reserve accounts directly from your AI agent.
Gumlet
12 toolsOptimize images and stream video with automatic format conversion, lazy loading, and CDN delivery that loads pages faster.
123FormBuilder
12 toolsBuild and manage online forms, collect submissions, and organize workspaces with AI-powered form automation for any workflow.