4,000+ servers built on vurb.ts
Vinkius

ORCID MCP Server for CrewAIGive CrewAI instant access to 13 tools to Create Item, Csv Search, Delete Item, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The ORCID MCP Server for CrewAI is a standout in the Knowledge Management category — giving your AI agent 13 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

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="ORCID Specialist",
    goal="Help users interact with ORCID effectively",
    backstory=(
        "You are an expert at leveraging ORCID 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 "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 13 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
ORCID
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 MCP Server

Connect to the ORCID (Open Researcher and Contributor ID) registry to identify and connect researchers with their professional activities across disciplines and borders.

When paired with CrewAI, ORCID becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ORCID 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

  • Record Retrieval — Fetch full summary views or specific biographical sections of any researcher using their 16-digit ORCID iD.
  • Activity Tracking — Query summaries of all activities including works, funding, and institutional affiliations.
  • Registry Search — Search the global ORCID database using Solr syntax to find researchers by name, email, or keywords.
  • Item Management — Deep dive into specific works or funding items using unique put-codes to retrieve full metadata.
  • Member API Features — For authorized users, create, update, or delete items within sections to keep researcher profiles synchronized.

The ORCID MCP Server exposes 13 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 13 ORCID tools available for CrewAI

When CrewAI connects to ORCID through Vinkius, your AI agent gets direct access to every tool listed below — spanning researcher-id, academic-publishing, data-attribution, 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.

create

Create item on ORCID

Requires Member API access and appropriate scopes. Add a new item to a section (Member API only)

csv

Csv search on ORCID

Search the ORCID registry and return CSV format

delete

Delete item on ORCID

Requires Member API access. Delete an item from a section (Member API only)

expanded

Expanded search on ORCID

Search the ORCID registry and return expanded metadata

get

Get activities on ORCID

Get summary of all activities for an ORCID record

get

Get item on ORCID

Get a specific item from a section using its put-code

get

Get person on ORCID

Get biographical section of an ORCID record

get

Get record on ORCID

Get summary view of the full ORCID record

get

Get section on ORCID

Get summary of a specific section

get

Get summary on ORCID

Requires Member API access. Get validated and self-asserted summary (Member API only)

register

Register webhook on ORCID

Requires Premium Member API. Register a webhook callback URL for an ORCID record (Premium only)

action

Search on ORCID

Supports fields like given-names, family-name, email, orcid, etc. Search the ORCID registry using Solr 3.6 syntax

update

Update item on ORCID

Requires Member API access. Update an existing item in a section (Member API only)

Connect ORCID to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai
02

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 13 tools from ORCID

Why Use CrewAI with the ORCID MCP Server

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

01

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

02

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

03

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

04

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 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the ORCID MCP Server delivers measurable value.

01

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

02

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

03

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

04

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

Example Prompts for ORCID in CrewAI

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

01

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

02

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

03

"List all the works associated with ORCID 0000-0002-1825-0097."

Troubleshooting ORCID MCP Server with CrewAI

Common issues when connecting ORCID to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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 + CrewAI FAQ

Common questions about integrating ORCID MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →