How do I find my Aliyun AccessKey and Endpoint?

Log in to the [Aliyun Console](https://oss.console.aliyun.com/), navigate to [AccessKey Management] to find your ID and Secret. Your Endpoint (e.g., `oss-cn-hangzhou.aliyuncs.com`) is visible in the bucket overview section.

What file types can I upload through the agent?

This MCP server is optimized for text-based content and metadata management. For large binary files (images, videos), it is recommended to use the public URL or native Aliyun tools for the actual transfer, while using the agent to manage metadata and listing.

Does this server handle signature calculation?

Yes! The server automatically calculates the required HMAC-SHA1 signature for every request using your provided AccessKey Secret, ensuring secure authorized communication with Aliyun OSS.

Aliyun OSS / 阿里云对象存储 MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Aliyun OSS / 阿里云对象存储
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Aliyun OSS / 阿里云对象存储 through Vinkius, pass the Edge URL in the `mcps` parameter and every Aliyun OSS / 阿里云对象存储 tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Aliyun OSS / 阿里云对象存储 Specialist",
    goal="Help users interact with Aliyun OSS / 阿里云对象存储 effectively",
    backstory=(
        "You are an expert at leveraging Aliyun OSS / 阿里云对象存储 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 Aliyun OSS / 阿里云对象存储 "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 Aliyun OSS / 阿里云对象存储 MCP Server

Empower your AI agent to orchestrate your cloud storage and asset management with Aliyun OSS (对象存储), the dominant object storage provider in China. By connecting Aliyun OSS to your agent, you transform complex file operations, bucket auditing, and metadata management into a natural conversation. Your agent can instantly upload text assets, retrieve detailed object metadata, list bucket contents with prefix filtering, and monitor storage status without you ever needing to navigate the comprehensive Aliyun Console. Whether you are conducting a digital asset audit or coordinating a content refresh, your agent acts as a real-time cloud storage assistant, providing accurate and fast results from a single, authorized source.

When paired with CrewAI, Aliyun OSS / 阿里云对象存储 becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Aliyun OSS / 阿里云对象存储 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

Asset Orchestration — Upload, delete, and manage text-based objects across your Aliyun OSS buckets.
Metadata Auditing — Retrieve detailed HTTP headers and custom metadata for any stored object.
Bucket Management — List objects with advanced filtering (prefix, marker) and verify bucket locations.
Public URL Generation — Automatically generate public endpoints for your shared assets.
System Monitoring — Monitor bucket configuration and API connectivity to ensure operational health.

The Aliyun OSS / 阿里云对象存储 MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Aliyun OSS / 阿里云对象存储 to CrewAI via MCP

Follow these steps to integrate the Aliyun OSS / 阿里云对象存储 MCP Server with CrewAI.

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 10 tools from Aliyun OSS / 阿里云对象存储

Why Use CrewAI with the Aliyun OSS / 阿里云对象存储 MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Aliyun OSS / 阿里云对象存储 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

Aliyun OSS / 阿里云对象存储 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Aliyun OSS / 阿里云对象存储 MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Aliyun OSS / 阿里云对象存储 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 Aliyun OSS / 阿里云对象存储, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Aliyun OSS / 阿里云对象存储 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 Aliyun OSS / 阿里云对象存储 against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Aliyun OSS / 阿里云对象存储 MCP Tools for CrewAI (10)

These 10 tools become available when you connect Aliyun OSS / 阿里云对象存储 to CrewAI via MCP:

copy_object

Uses x-oss-copy-source header. Copy an object within the bucket

delete_object

Delete an object from OSS

download_object_text

Best for text/JSON files. Download an object as text

get_bucket_acl

Get bucket access control list

get_bucket_info

Get bucket configuration

get_bucket_location

g., oss-cn-hangzhou) where your bucket is located. Get bucket region

get_bucket_statistics

Get bucket storage statistics

get_object_metadata

Get object metadata (HEAD)

list_objects

Use prefix to filter by path, marker for pagination. List objects in the bucket

upload_object

Max 5GB per request. Upload text content to OSS

Example Prompts for Aliyun OSS / 阿里云对象存储 in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Aliyun OSS / 阿里云对象存储 immediately.

"List all objects in my Aliyun OSS bucket with prefix 'images/'."

"Upload this text to 'config/settings.json': '{"theme": "dark"}'."

"What is the public URL for 'docs/manual.pdf'?"

Troubleshooting Aliyun OSS / 阿里云对象存储 MCP Server with CrewAI

Common issues when connecting Aliyun OSS / 阿里云对象存储 to CrewAI through the 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.

Aliyun OSS / 阿里云对象存储 + CrewAI FAQ

Common questions about integrating Aliyun OSS / 阿里云对象存储 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.