How to Use the Amazon S3 Bucket MCP in LlamaIndex

Q: Can I build a RAG pipeline using the Amazon S3 Bucket server and LlamaIndex?

Yes. LlamaIndex uses listobjects to find target files and getobjectdata to pull the text content directly into its document parsers.

Q: How do I limit which files LlamaIndex can read from my Amazon S3 Bucket?

You configure the prefix filter in listobjects to restrict your LlamaIndex agent to a specific folder inside your Amazon S3 Bucket.

Q: How does the agent know if a file has changed?

The LlamaIndex agent calls getobjectmetadata to check the ETag or last-modified timestamp of the S3 file before running the ingestion pipeline again.

Q: How is my Amazon S3 Bucket policy data protected?

All bucket policy details retrieved via getbucketpolicy are processed entirely in memory inside a zero-trust V8 sandbox and never written to persistent logs.

Index live Amazon S3 Bucket files directly into LlamaIndex vector stores for ground-truth RAG applications.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Amazon S3 Bucket MCP to LlamaIndex

Create your Vinkius account to connect Amazon S3 Bucket to LlamaIndex 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 Amazon S3 Bucket with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index Live Objects for LlamaIndex RAG

`get_object_data` fetches the raw contents of your S3 files using this MCP server so LlamaIndex can parse and chunk them into vector nodes. Your LlamaIndex query engines get real-time access to S3 bucket contents without manual sync scripts. You use `list_objects` to scan the S3 bucket for new files, feeding only the updated keys into your LlamaIndex ingestion pipeline. This keeps your LlamaIndex vector index fresh and accurate with real S3 data.

Verify Metadata Before Indexing via LlamaIndex

`get_object_metadata` retrieves system and user-defined S3 metadata for any file before LlamaIndex starts parsing it. This S3 metadata becomes LlamaIndex node attributes, allowing for precise filtering during semantic search. By checking S3 file sizes and content types first, your LlamaIndex pipeline avoids wasting tokens on unparseable binary files. Your LlamaIndex agent only indexes what it actually needs from the S3 bucket.

Manage Index Storage with this MCP Server

`put_object` saves serialized LlamaIndex index schemas and query logs back to your S3 bucket directly from your workflow. Your LlamaIndex agent persists its own knowledge state in S3 between runs without local disk access. The LlamaIndex agent uses `delete_object` to clean up outdated index chunks or temporary files in S3. This maintains a lean, cost-effective S3 storage footprint automatically for your LlamaIndex application.

Setup guide

Set up Amazon S3 Bucket MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Amazon S3 Bucket MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Amazon S3 Bucket tools.",
)
response = await agent.run("List recent Amazon S3 Bucket data")

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 Amazon S3 Bucket. 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 Amazon S3 Bucket 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 Amazon S3 Bucket MCP in LlamaIndex

Yes. LlamaIndex uses `list_objects` to find target files and `get_object_data` to pull the text content directly into its document parsers.

You configure the prefix filter in `list_objects` to restrict your LlamaIndex agent to a specific folder inside your Amazon S3 Bucket.

Yes. The LlamaIndex MCP adapter handles async execution, allowing tools like `get_object_data` to run concurrently during document ingestion.

The LlamaIndex agent calls `get_object_metadata` to check the ETag or last-modified timestamp of the S3 file before running the ingestion pipeline again.

All bucket policy details retrieved via `get_bucket_policy` are processed entirely in memory inside a zero-trust V8 sandbox and never written to persistent logs.

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