4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Figshare MCP Server

Bring Open Science
to CrewAI

Learn how to connect Figshare to CrewAI and start using 20 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Complete File UploadCreate CollectionCreate Private ArticleCreate ProjectDelete ArticleGet ArticleGet Article DownloadsGet Article ViewsGet Custom FieldsGet File DetailsGet Hrfeed UploadInitiate File UploadList Article FilesList Public ArticlesList Public CollectionsList Public ProjectsSearch ArticlesSearch CollectionsSearch ProjectsUpdate Article

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Figshare

What is the Figshare MCP Server?

Connect your Figshare account to any AI agent to streamline your research data management and publication workflows through natural conversation.

What you can do

  • Article Management — List public articles, fetch specific article details, and create, update, or delete private articles in your account.
  • File Handling — List files associated with articles, initiate multi-part S3 uploads, and track file details for your research datasets.
  • Collections & Projects — Create and list public collections and projects to organize your scholarly output effectively.
  • Metadata Control — Update titles, descriptions, and other metadata for your articles to ensure they are discoverable and well-documented.

How it works

  1. Subscribe to this server
  2. Enter your Figshare Personal Access Token
  3. Start managing your research repository from Claude, Cursor, or any MCP-compatible client

No more manual navigation through repository interfaces to check upload statuses or update metadata. Your AI acts as a research data manager.

Who is this for?

  • Researchers & Academics — quickly upload datasets, update article descriptions, and check publication statuses without leaving your workspace.
  • Data Managers — automate the organization of large collections and projects across institutional repositories.
  • Librarians & Archivists — query public research outputs and manage metadata updates efficiently.

Built-in capabilities (20)

complete_file_upload

Complete a file upload

create_collection

Create a new collection

create_private_article

Create a new private article

create_project

Create a new project

delete_article

Delete an article

get_article

Get details of a specific article

get_article_downloads

Get total downloads for an article

get_article_views

Get total views for an article

get_custom_fields

Get custom metadata fields for the institution

get_file_details

Get file details

get_hrfeed_upload

Get HR feed upload details

initiate_file_upload

Initiate a file upload for an article

list_article_files

List files for an article

list_public_articles

List public articles

list_public_collections

List public collections

list_public_projects

List public projects

search_articles

Advanced search for articles

search_collections

Advanced search for collections

search_projects

Advanced search for projects

update_article

Update an existing article

Why CrewAI?

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

  • 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

See it in action

Figshare in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Figshare and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Figshare to CrewAI 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Figshare in CrewAI

The Figshare 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 20 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI 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.

Figshare
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

The Vinkius Advantage

How Vinkius secures Figshare for CrewAI

Every tool call from CrewAI to the Figshare MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I upload files to a Figshare article using this integration?

Yes. You can use initiate_file_upload to start the process and complete_file_upload once the data transfer is finished. You can also use list_article_files to verify the contents of any article.

02

How do I create a new private draft for my research?

Simply ask the agent to use the create_private_article tool. Provide a title and an optional description, and the agent will generate a new private entry in your Figshare account.

03

Is it possible to organize my articles into projects or collections?

Absolutely. You can use create_project or create_collection to set up organizational structures, and use list_public_projects or list_public_collections to browse existing ones.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →