ORCID (Researcher IDs) MCP Server for CrewAIGive CrewAI instant access to 14 tools to Add Item, Csv Search, Delete Item, and more

Name: ORCID (Researcher IDs)
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Connect your CrewAI agents to ORCID (Researcher IDs) through Vinkius, pass the Edge URL in the `mcps` parameter and every ORCID (Researcher IDs) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The ORCID (Researcher IDs) MCP Server for CrewAI is a standout in the Knowledge Management category — giving your AI agent 14 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="ORCID (Researcher IDs) Specialist",
    goal="Help users interact with ORCID (Researcher IDs) effectively",
    backstory=(
        "You are an expert at leveraging ORCID (Researcher IDs) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in ORCID (Researcher IDs) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 14 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About ORCID (Researcher IDs) MCP Server

Connect the ORCID registry to your AI agent to seamlessly navigate the global ecosystem of researcher identifiers and scholarly records.

When paired with CrewAI, ORCID (Researcher IDs) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ORCID (Researcher IDs) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Registry Search — Perform standard or expanded Solr searches to find researchers by name, institution, or keywords using search and expanded_search.
Profile Summaries — Retrieve complete researcher records, including biographical details and activity summaries, via get_record and get_activities.
Works & Funding — Inspect specific research outputs and funding history using get_works or drill down into specific items with get_section_item.
Trust Markers — Access validated trust markers for records using get_summary (requires Member API).
Record Management — Add or update items in an ORCID record directly through the agent using add_item and update_item (requires Member API).

The ORCID (Researcher IDs) MCP Server exposes 14 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 14 ORCID (Researcher IDs) tools available for CrewAI

When CrewAI connects to ORCID (Researcher IDs) through Vinkius, your AI agent gets direct access to every tool listed below — spanning researcher-search, academic-profile, solr-search, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add item on ORCID (Researcher IDs)

Requires Member API access token with /activities/update or /person/update scope. Add a new item to an ORCID record (Member API only)

csv

Csv search on ORCID (Researcher IDs)

Search the ORCID registry and return CSV data

delete

Delete item on ORCID (Researcher IDs)

Requires Member API access token. Delete an item from an ORCID record (Member API only)

expanded

Expanded search on ORCID (Researcher IDs)

Search the ORCID registry (Expanded)

get

Get activities on ORCID (Researcher IDs)

Get summary of all activities for an ORCID record

get

Get person on ORCID (Researcher IDs)

Get biographical section of an ORCID record

get

Get record on ORCID (Researcher IDs)

Get full summary of an ORCID record

get

Get section item on ORCID (Researcher IDs)

Get full details for a specific item in an ORCID record

get

Get summary on ORCID (Researcher IDs)

Requires Member API access token. Get validated trust markers (Member API only)

get

Get works on ORCID (Researcher IDs)

Get summary of research works for an ORCID record

Register webhook on ORCID (Researcher IDs)

Requires /webhook scope. Register a webhook for an ORCID record (Premium Member API only)

action

Search on ORCID (Researcher IDs)

Search the ORCID registry (Standard)

unregister

Unregister webhook on ORCID (Researcher IDs)

Unregister a webhook for an ORCID record (Premium Member API only)

update

Update item on ORCID (Researcher IDs)

Requires Member API access token. Update an existing item in an ORCID record (Member API only)

Connect ORCID (Researcher IDs) to CrewAI via MCP

Follow these steps to wire ORCID (Researcher IDs) into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 14 tools from ORCID (Researcher IDs)

Why Use CrewAI with the ORCID (Researcher IDs) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with ORCID (Researcher IDs) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

ORCID (Researcher IDs) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the ORCID (Researcher IDs) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries ORCID (Researcher IDs) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries ORCID (Researcher IDs), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain ORCID (Researcher IDs) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries ORCID (Researcher IDs) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for ORCID (Researcher IDs) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with ORCID (Researcher IDs) immediately.

"Search the ORCID registry for researchers with the family name 'Einstein'."

"Get the biographical details for ORCID 0000-0002-1825-0097."

"List all research works for ORCID 0000-0003-1415-9265."

Troubleshooting ORCID (Researcher IDs) MCP Server with CrewAI

Common issues when connecting ORCID (Researcher IDs) to CrewAI through Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

ORCID (Researcher IDs) + CrewAI FAQ

Common questions about integrating ORCID (Researcher IDs) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.