Figshare MCP Server for CrewAIGive CrewAI instant access to 20 tools to Complete File Upload, Create Collection, Create Private Article, and more

Name: Figshare
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Connect your CrewAI agents to Figshare through Vinkius, pass the Edge URL in the `mcps` parameter and every Figshare 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 Figshare MCP Server for CrewAI is a standout in the Data Management category — giving your AI agent 20 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="Figshare Specialist",
    goal="Help users interact with Figshare effectively",
    backstory=(
        "You are an expert at leveraging Figshare 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 Figshare "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 20 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 Figshare MCP Server

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

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.

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.

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

When CrewAI connects to Figshare through Vinkius, your AI agent gets direct access to every tool listed below — spanning open-science, research-data, academic-publishing, 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.

complete

Complete file upload on Figshare

Complete a file upload

create

Create collection on Figshare

Create a new collection

create

Create private article on Figshare

Create a new private article

create

Create project on Figshare

Create a new project

delete

Delete article on Figshare

Delete an article

get

Get article on Figshare

Get details of a specific article

get

Get article downloads on Figshare

Get total downloads for an article

get

Get article views on Figshare

Get total views for an article

get

Get custom fields on Figshare

Get custom metadata fields for the institution

get

Get file details on Figshare

Get file details

get

Get hrfeed upload on Figshare

Get HR feed upload details

initiate

Initiate file upload on Figshare

Initiate a file upload for an article

list

List article files on Figshare

List files for an article

list

List public articles on Figshare

List public articles

list

List public collections on Figshare

List public collections

list

List public projects on Figshare

List public projects

Search articles on Figshare

Advanced search for articles

Search collections on Figshare

Advanced search for collections

Search projects on Figshare

Advanced search for projects

update

Update article on Figshare

Update an existing article

Connect Figshare to CrewAI via MCP

Follow these steps to wire Figshare 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 20 tools from Figshare

Why Use CrewAI with the Figshare MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Figshare 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

Figshare + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Figshare 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 Figshare, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Figshare 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 Figshare against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Figshare in CrewAI

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

"List the most recent public articles on Figshare."

"Create a private article titled 'Lab Results Q4' with the description 'Raw data from the December experiments'."

"Show me all files attached to article 1234567."

Troubleshooting Figshare MCP Server with CrewAI

Common issues when connecting Figshare 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.

Figshare + CrewAI FAQ

Common questions about integrating Figshare 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.