How to Use the Azure Blob Container MCP in CrewAI

Q: Can a CrewAI team work together on files in an Azure Blob Container?

Yes, that's a core strength. One agent can use listblobs to find files, then pass the list to another agent in the crew. That second agent can then use getblob to read each file for analysis, all as part of a single, collaborative task.

Q: How do I give different CrewAI agents different permissions for an Azure Blob Container?

When you define an agent, use the toolfilter argument with the MCP server configuration. This lets you create a list of allowed tool names, like 'getblob', 'listblobs', for that specific agent. It's an effective way to enforce roles within your crew.

Q: What's the easiest way to add these Azure tools to my CrewAI agent?

Just pass your Vinkius MCP URL into the mcps list when you create your Agent. CrewAI handles the introspection, automatically discovering and equipping the agent with the listblobs, getblob, putblob, and deleteblob tools.

Deploy autonomous agent crews to manage your Azure Blob Storage. Let one agent organize files while another analyzes them with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Azure Blob Container MCP to CrewAI

Create your Vinkius account to connect Azure Blob Container to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Azure Blob Container with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Divide and Conquer File Management

Assign specialized roles to your agents for safer, more focused operations. Create a 'Librarian' agent that can only use `list_blobs` and `get_blob` for read-only tasks. Then, create a 'Janitor' agent that has the `delete_blob` tool for cleanup duties. CrewAI's `tool_filter` option makes this possible. When defining each agent, you specify which of this MCP server's tools it can access. This enforces the principle of least privilege, making your autonomous crew more robust and predictable.

Autonomous Monitoring and Reporting

Build a hands-off monitoring system. A 'Watcher' agent can run on a schedule, using `list_blobs` to check an 'uploads' directory. When it spots a new file, it passes the filename to a 'Reporter' agent on the same crew. The Reporter agent then uses `get_blob` to read the new file's content, generates a summary, and could use another tool to send a Slack message. This entire process is managed by the CrewAI framework, giving you an autonomous team that keeps an eye on your data for you.

Collaborative Data Processing with your CrewAI MCP Server

Tackle complex jobs by breaking them down. Imagine you need to find all error logs from the past day, consolidate them, and summarize the findings. A 'Researcher' agent can use `list_blobs` to find the relevant log files. It then passes that list to a 'Compiler' agent, which loops through the list, calling `get_blob` on each file to read its contents. Finally, a 'Summarizer' agent takes the combined text and uses `put_blob` to save a clean report back to the container. This MCP server provides the tools; CrewAI provides the teamwork.

Setup guide

Set up Azure Blob Container MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Azure Blob Container tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Azure Blob Container Analyst",
    goal="Access and analyze Azure Blob Container data via MCP.",
    backstory="Expert analyst with direct Azure Blob Container access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Azure Blob Container transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Azure Blob Container Analyst",
        goal="Access and analyze Azure Blob Container data via MCP.",
        backstory="Expert analyst with direct Azure Blob Container access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Azure Blob Container transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Azure Blob Container. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Azure Blob Container now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Azure Blob Container MCP in CrewAI

Yes, that's a core strength. One agent can use `list_blobs` to find files, then pass the list to another agent in the crew. That second agent can then use `get_blob` to read each file for analysis, all as part of a single, collaborative task.

When you define an agent, use the `tool_filter` argument with the MCP server configuration. This lets you create a list of allowed tool names, like `['get_blob', 'list_blobs']`, for that specific agent. It's an effective way to enforce roles within your crew.

Definitely. You can design an agent with a recurring task that calls the `list_blobs` tool. By comparing the new output with the last known state, it can identify new files and delegate tasks to other agents to process them.

Just pass your Vinkius MCP URL into the `mcps` list when you create your Agent. CrewAI handles the introspection, automatically discovering and equipping the agent with the `list_blobs`, `get_blob`, `put_blob`, and `delete_blob` tools.

Security is layered. The MCP server itself is restricted to one container, preventing any access beyond it. Your crew's tool calls are sent over an encrypted channel, and Vinkius executes them in single-use, isolated sandboxes. Your actual blob contents are never stored or logged by our platform.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript